celery 5.0.0 with Django==3.0.10 emits CDeprecationWarning. Following the advise breaks the app #6366
Description
Congrats on the v5 release 👏 and thank you for maintaining such a wonderful piece of software. Much appreciated.
I updated from celery==4.4.7 to celery==5.0.0 today and I'm using celery with Django 3.0.10. Celery produces this message - and others - after starting:
[2020-09-25 11:31:17,362: WARNING/MainProcess] /var/www/brwnppr/dev/env/lib/python3.7/site-packages/celery/app/utils.py:206: CDeprecationWarning:
The 'CELERY_TASK_SERIALIZER' setting is deprecated and scheduled for removal in
version 6.0.0. Use the task_serializer instead
alternative=f'Use the {_TO_NEW_KEY[setting]} instead')
[2020-09-25 11:31:17,364: WARNING/MainProcess] /var/www/brwnppr/dev/env/lib/python3.7/site-packages/celery/app/utils.py:206: CDeprecationWarning:
The 'CELERYBEAT_SCHEDULE' setting is deprecated and scheduled for removal in
version 6.0.0. Use the beat_schedule instead
alternative=f'Use the {_TO_NEW_KEY[setting]} instead')
[2020-09-25 11:31:17,364: WARNING/MainProcess] /var/www/brwnppr/dev/env/lib/python3.7/site-packages/celery/app/utils.py:206: CDeprecationWarning:
The 'CELERY_DEFAULT_QUEUE' setting is deprecated and scheduled for removal in
version 6.0.0. Use the task_default_queue instead
alternative=f'Use the {_TO_NEW_KEY[setting]} instead')
[2020-09-25 11:31:17,365: WARNING/MainProcess] /var/www/brwnppr/dev/env/lib/python3.7/site-packages/celery/app/utils.py:206: CDeprecationWarning:
The 'CELERY_ACCEPT_CONTENT' setting is deprecated and scheduled for removal in
version 6.0.0. Use the accept_content instead
alternative=f'Use the {_TO_NEW_KEY[setting]} instead')
[2020-09-25 11:31:17,365: WARNING/MainProcess] /var/www/brwnppr/dev/env/lib/python3.7/site-packages/celery/app/utils.py:206: CDeprecationWarning:
The 'BROKER_URL' setting is deprecated and scheduled for removal in
version 6.0.0. Use the broker_url instead
alternative=f'Use the {_TO_NEW_KEY[setting]} instead')
[2020-09-25 11:31:17,366: WARNING/MainProcess] /var/www/brwnppr/dev/env/lib/python3.7/site-packages/celery/app/utils.py:206: CDeprecationWarning:
The 'CELERY_RESULT_SERIALIZER' setting is deprecated and scheduled for removal in
version 6.0.0. Use the result_serializer instead
alternative=f'Use the {_TO_NEW_KEY[setting]} instead')
[2020-09-25 11:31:17,367: WARNING/MainProcess] /var/www/brwnppr/dev/env/lib/python3.7/site-packages/celery/app/utils.py:206: CDeprecationWarning:
The 'CELERY_RESULT_BACKEND' setting is deprecated and scheduled for removal in
version 6.0.0. Use the result_serializer instead
alternative=f'Use the {_TO_NEW_KEY[setting]} instead')
[2020-09-25 11:31:17,367: WARNING/MainProcess] /var/www/brwnppr/dev/env/lib/python3.7/site-packages/celery/app/utils.py:206: CDeprecationWarning:
The 'CELERY_RESULT_BACKEND' setting is deprecated and scheduled for removal in
version 6.0.0. Use the result_backend instead
alternative=f'Use the {_TO_NEW_KEY[setting]} instead')
[2020-09-25 11:31:17,367: WARNING/MainProcess] Please run `celery upgrade settings path/to/settings.py` to avoid these warnings and to allow a smoother upgrade to Celery 6.0.
I ran the celery upgrade command on the Django project settings and it worked beautifully. Unfortunately the application appears to block after the upgrade command and I think that blocking is caused by celery falling back to amqp while the project I'm working on uses redis as the broker. The Django application itself blocks due to it trying to starting a task which fails for the same reason.
Reverted the settings - thanks for keeping a .orig and it's up and running again.
Now I have been looking through the code to see if I could come up with a PR to suppress this message, but that appears to be kind of hard due to the way the configuration is processed. I'll see if I can come up with something.