New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove configuration compatibility shims from 3.x #6327
Comments
I gave this a shot. |
I have a branch that removes support for the old setting names.
I'm not so sure anymore we should do this in 5.0. What do you think? |
we should not remove them in v5 for easier migration |
I don't believe accepting the all-caps version was deprecated? The documentation around Django seems to say that the all-caps version (and prefixing them) is still allowed. |
Here's what I think (and what I implemented): |
Celery 4.0 introduced new configuration setting names (see the documentation), but maintained compatibility with the old names. This seems to be a source of confusion (and I've witnessed numerous issues filed that are due to configuration problems). 5.0 seems like a good time to simplify this and have only a single standard form for these configuration variables.
I believe the code lives around [here]
celery/celery/app/defaults.py
Lines 76 to 341 in 5b86b35
The text was updated successfully, but these errors were encountered: