Celery not picking CELERY_ALWAYS_EAGER settings
CELERY_ALWAYS_EAGER
has been renamed to CELERY_TASK_ALWAYS_EAGER
in version 4.0+.
More accurately, all-caps settings have been deprecated in favor of directly configuring the celery app object, and several have been namespaced to either use task_
or worker_
as a prefix. Because there's still backwards-compatability with all-caps settings, this indirectly renamed the all-caps setting as well.
From the changelog:
The celery_ prefix has also been removed, and task related settings from this name-space is now prefixed by task_, worker related settings with worker_.
AlexA
Freelance Python developer. Data engineer. LinkedIn Profile: https://www.linkedin.com/in/alexey-a-181a614/ AWS Certified Solutions Architect associate Tools: Django, Python, AWS, Celery, mysql, Postgresql, jquery, Backbone.js
Updated on June 07, 2022Comments
-
AlexA about 2 years
I am running Django 1.8 + Celery 4.0.2 Celery is configured well and can run my Django tasks locally on redis backend. But when I try to use
CELERY_ALWAYS_EAGER = True
settings, this settings has no effect. Which is not the case with other settings, e.g.CELERY_TIMEZONE
Specifically, in
pdb
I see thatapp.conf.task_always_eager
isFalse
lib/python2.7/site-packages/celery/app/task.py(520)apply_async() So somehow CELERY_ALWAYS_EAGER is not picked up and has no effect on app.conf.task_always_eager
More info from pdb:
> app.conf.get('CELERY_ALWAYS_EAGER') > True > app.conf.task_always_eager > False
What can cause this? I know that Celery 4.x is in transition from old setting names to new ones, but they still promise old settings names still would be used as well.