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
Django 1.9 removed get_cache from django.core.cache #149
Comments
Not sure how to trigger that. That code branch is only called for backward compatibility, if the first import in https://github.com/mbi/django-rosetta/blob/develop/rosetta/storage.py#L10 fails. It won't ever be called on Django 1.9, or am I missing something? |
It's me who missed something. I had problems with behavior with web interface so i tried to switch to different cache then the default LocMem. I put MemCached to setting and the problem has begun. |
Sweet, thank you. |
I'm also getting this error in django 1.9 with rosetta 0.7.11 when I use Memcached cache backend. Here's the full traceback:
If I remove
If I remove my
I've running this configuration in production using django 1.7 and rosetta 0.7.4 and don't see this error. Do I have my CACHES misconfigured? Thanks! |
Hi @saschwarz. Have you overridden I.e. what is the output of this?
It should match one of your cache backends, probably |
Thanks for the fast reply! I haven't overridden it:
|
Okay interesting, does any of these lines throw an error?
|
That gave the answer:
In my new Django 1.9 venv I hadn't installed memcache! I hadn't noticed it because the new rosetta code checked that I had an incompatible cache backend and when I enabled my production backed in dev the ImportError was being caught/handled by: https://github.com/mbi/django-rosetta/blob/develop/rosetta/poutil.py#L12 I guess you could do something to not hide that type of traceback:
But it could be brittle... or my situation is unusual... I could create a PR if you think this is valuable. Sorry to have taken your time for my mistake. Thanks so much for all your help debugging this! |
In your case the missing memcached exception was swallowed by that ImportError handler, but actually we no longer need that, as Rosetta only supports Django 1.7+ now. I've removed it in c80f2db |
Rosetta 0.7.8, Django 1.9. Using memcached backend. Error:
Django 1.9 release notes: django.core.cache.get_cache is removed
The text was updated successfully, but these errors were encountered: