-
Notifications
You must be signed in to change notification settings - Fork 30
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
ImportError: cannot import name BACKEND_ALIASES #9
Comments
which celery version? |
Oops, I forgot to include that. This is happening with 4.0.2. |
I just downgraded to version 3.1.23 and it seems to be working better, I will stick with Celery 3. Thank you! |
This could be also fixed with a stricter dependency in the packaging. (as well as the fix noted in the comment above). |
Just hit this issue, @miki725 can you create a release? This repo hasn't been updated in a while. Is there a better way (now 2018) to use redis as a results backend with sentinel? I note Celery now supports sentinel as a broker, but not as a results backend: http://docs.celeryproject.org/en/latest/getting-started/brokers/redis.html#results. |
Do we have a plan to create a new release with the latest code? |
Hi, I would like to use this package but I get the following error:
I thought there was an issue with $PYTHONPATH but
from celery import backends
works fine. Do you have any advice?I am running Mac OS X, Python 2.7.12. Thanks for taking a look!
The text was updated successfully, but these errors were encountered: