-
-
Notifications
You must be signed in to change notification settings - Fork 317
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
cache_url
doesn't handle backend properly.
#464
Comments
Hi @RemiDesgrange, Thank you for bringing this issue to our attention. To better understand the problem and evaluate your proposed solution, could you please provide a test case that reproduces the issue? A test that highlights the current problems and needs would be particularly helpful. |
Ok, in what form this solution should be provided ? The Thx. |
Providing a unit test would be ideal |
in your example you mention
i am guessing it is intentional, although there is no documentation the
A few other shortcuts support the same mechanism, like edit: correction, here's a test: django-environ/tests/test_cache.py Line 173 in df301b6
/cc @sergeyklay looks like this is properly working and tested; may need docs. |
Sorry Thanks for the clarification. |
I have no idea if it's bug or a feature:
let's say I have 2 env var:
in
settings.py
the backend is set here
django-environ/environ/environ.py
Line 629 in 8874288
django.core.cache.backends.dummy.DummyCache
.But the
backend
key is reset to the default value 44 lines later heredjango-environ/environ/environ.py
Lines 673 to 674 in 8874288
no idea if this is intentional or not. I the fix is only removing the
if backend
line I'll be happy to submit a PR.The text was updated successfully, but these errors were encountered: