Ideally try to avoid using Celery at all. It's the most consistently buggy, poorly documented, worst quality major Python project I have used so far. Here is a

Ideally try to avoid using Celery at all. It's the most consistently buggy, poorly documented, worst quality major Python project I have used so far. Here is a fresh example: they deprecated CELERY_ prefixes in Django settings for some reason, which makes zero sense [1]. But because it's Celery, they only warn on a few properties but not others, and the tool they ship inexplicably renamed completely unrelated settings for me [2]. And yes, apparently the new way doesn't work either [3]. It's very characteristic of what I've seen from Celery over the last few years of working with it. If you are doing anything greenfield, it's best to avoid it altogether. [1] https://stackoverflow.com/questions/65554242/celery-imports-celery-result-backend-deprecated-how-to-use-alternative https://stackoverflow.com/questions/65554242/celery-imports-... [2] https://twitter.com/lambdadmitry/status/1468337594358546435?s=21 https://twitter.com/lambdadmitry/status/1468337594358546435?... [3] https://github.com/celery/celery/issues/7140 https://github.com/celery/celery/issues/7140