Skip to content
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

Open
dcox opened this issue Feb 28, 2017 · 7 comments
Open

ImportError: cannot import name BACKEND_ALIASES #9

dcox opened this issue Feb 28, 2017 · 7 comments

Comments

@dcox
Copy link

dcox commented Feb 28, 2017

Hi, I would like to use this package but I get the following error:

>>> from celery_redis_sentinel import register
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/local/lib/python2.7/dist-packages/celery_redis_sentinel/register.py", line 4, in <module>
    from celery.backends import BACKEND_ALIASES
ImportError: cannot import name BACKEND_ALIASES

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!

@miki725
Copy link
Contributor

miki725 commented Feb 28, 2017

which celery version?

@dcox
Copy link
Author

dcox commented Feb 28, 2017

Oops, I forgot to include that. This is happening with 4.0.2.

@dcox
Copy link
Author

dcox commented Feb 28, 2017

I just downgraded to version 3.1.23 and it seems to be working better, I will stick with Celery 3. Thank you!

miki725 added a commit that referenced this issue Mar 15, 2017
Add compatibility with celery 4 #9
@tsionyx
Copy link

tsionyx commented May 23, 2017

I see this was fixed in 1696912. @miki725 could you please upload the the last version on pypi?

@arthurzenika
Copy link

This could be also fixed with a stricter dependency in the packaging. (as well as the fix noted in the comment above).

@wjdp
Copy link

wjdp commented Feb 12, 2018

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.

@HungPhann
Copy link

Do we have a plan to create a new release with the latest code?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants