sum(numbers) @shared_task def count_widgets(): return Widget.objects.count() @shared_task def rename_widget(widget_id, name): w = Widget.objects.get(id=widget_id) w.name = name w.save() See in this version for backward compatibility, they will be removed in Celery 5.0, so make sure you rename these ASAP to make sure it won’t break for that release. Chances are that you’ll only use the first sqlalchemy_* -> database_*. The sqlalchemy_ named settings won’t work at all in this version so you need to rename them. This is a last minute change, and as they were not supported in 3.1 we will not be providing

sum(numbers) @shared_task def count_widgets(): return Widget.objects.count() @shared_task def rename_widget(widget_id, name): w = Widget.objects.get(id=widget_id) w.name = name w.save() See in this version for backward compatibility, they will be removed in Celery 5.0, so make sure you rename these ASAP to make sure it won’t break for that release. Chances are that you’ll only use the first sqlalchemy_* -> database_*. The sqlalchemy_ named settings won’t work at all in this version so you need to rename them. This is a last minute change, and as they were not supported in 3.1 we will not be providing

sum(numbers) @shared_task def count_widgets(): return Widget.objects.count() @shared_task def rename_widget(widget_id, name): w = Widget.objects.get(id=widget_id) w.name = name w.save() See in this version for backward compatibility, they will be removed in Celery 5.0, so make sure you rename these ASAP to make sure it won’t break for that release. Chances are that you’ll only use the first sqlalchemy_* -> database_*. The sqlalchemy_ named settings won’t work at all in this version so you need to rename them. This is a last minute change, and as they were not supported in 3.1 we will not be providing

sum(numbers) @shared_task def count_widgets(): return Widget.objects.count() @shared_task def rename_widget(widget_id, name): w = Widget.objects.get(id=widget_id) w.name = name w.save() See in this version for backward compatibility, they will be removed in Celery 5.0, so make sure you rename these ASAP to make sure it won’t break for that release. Chances are that you’ll only use the first sqlalchemy_* -> database_*. The sqlalchemy_ named settings won’t work at all in this version so you need to rename them. This is a last minute change, and as they were not supported in 3.1 we will not be providing

sqlalchemy_* -> database_*. The sqlalchemy_ named settings won’t work at all in this version so you need to rename them. This is a last minute change, and as they were not supported in 3.1 we will not be providing in this version for backward compatibility, they will be removed in Celery 5.0, so make sure you rename these ASAP to make sure it won’t break for that release. Chances are that you’ll only use the first naming scheme. We now support consuming from an arbitrary number of queues. To do this we had to rename the configuration syntax. If you use any of the custom AMQP routing options (queue/exchange/routing_key

sqlalchemy_* -> database_*. The sqlalchemy_ named settings won’t work at all in this version so you need to rename them. This is a last minute change, and as they were not supported in 3.1 we will not be providing in this version for backward compatibility, they will be removed in Celery 5.0, so make sure you rename these ASAP to make sure it won’t break for that release. Chances are that you’ll only use the first naming scheme. We now support consuming from an arbitrary number of queues. To do this we had to rename the configuration syntax. If you use any of the custom AMQP routing options (queue/exchange/routing_key

naming scheme. • We now support consuming from an arbitrary number of queues. To do this we had to rename the configuration syntax. If you use any of the custom AMQP routing options (queue/exchange/routing_key

naming scheme. We now support consuming from an arbitrary number of queues. To do this we had to rename the configuration syntax. If you use any of the custom AMQP routing options (queue/exchange/routing_key

sum(numbers) @shared_task def count_widgets(): return Widget.objects.count() @shared_task def rename_widget(widget_id, name): w = Widget.objects.get(id=widget_id) w.name = name w.save() See in this version for backward compatibility, they will be removed in Celery 5.0, so make sure you rename these ASAP to make sure it won’t break for that release. Chances are that you’ll only use the first sqlalchemy_* -> database_*. The sqlalchemy_ named settings won’t work at all in this version so you need to rename them. This is a last minute change, and as they were not supported in 3.1 we will not be providing

sum(numbers) @shared_task def count_widgets(): return Widget.objects.count() @shared_task def rename_widget(widget_id, name): w = Widget.objects.get(id=widget_id) w.name = name w.save() See in this version for backward compatibility, they will be removed in Celery 5.0, so make sure you rename these ASAP to make sure it won’t break for that release. Chances are that you’ll only use the first sqlalchemy_* -> database_*. The sqlalchemy_ named settings won’t work at all in this version so you need to rename them. This is a last minute change, and as they were not supported in 3.1 we will not be providing