-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
No module named 'celery.backends.amqp' or KeyError: 'backend' #6384
Comments
The amqp backend was deprecated as documented in the release notes. |
A temporary fix is to |
temporary fix until its updated: use CELERY_RESULT_BACKEND = "rpc://" instead |
@thedrow Your release notes link is broken. The docs still imply RabbitMQ and amqp support is available. Have the docs not been updated or am I misreading them? I've tried changing my |
Hello. I'm wondering why is this issue closed? Is the backend supported or not? It is according to the documentation. https://docs.celeryproject.org/en/stable/reference/celery.app.amqp.html Upgrading celery o version >5 is a requirement for our product, given CVE-2021-23727. Are we supposed to move to rpc? Thank you for your amazing work |
Ok, I found the answer in the 5.2 release notes nevermind. Thankyou |
Still listed in the docs as the default and an "Excellent choice" https://docs.celeryproject.org/en/stable/getting-started/first-steps-with-celery.html#rabbitmq |
I'm wondering, how can we participate in updating the documentation? |
As broaker/transport, not as result backend |
Pull requests are welcome. |
The amqp backend is still on the |
If so, yes |
I encountered this issue while running Celery on a docker container. Changing my |
Problem with Python 3.8.5 / Flask and Celery 5.0
Python code:
init.py
run.py
The text was updated successfully, but these errors were encountered: