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

Does django-cachalot lib support the new django.core.cache.backends.redis.RedisCache cache backend in Django version 4.0? #222

Open
vuphan-agilityio opened this issue Nov 3, 2022 · 4 comments · May be fixed by #264

Comments

@vuphan-agilityio
Copy link

vuphan-agilityio commented Nov 3, 2022

Question

The new django.core.cache.backends.redis.RedisCache cache backend provides built-in support for caching with Redis in Django version 4.0 and I used it in my application.
I've used the latest version django-cachalot and got this warning: Cache backend 'django.core.cache.backends.redis.RedisCache' is not supported by django-cachalot.
My question is: Does django-cachalot lib support the new django.core.cache.backends.redis.RedisCache cache backend in Django version 4.0?
Please help answer my question, thanks!

@Andrew-Chen-Wang
Copy link
Collaborator

It needs to be added to our test matrix to be supported. For now, you can mute the warning: cachalot.W003

@vuphan-agilityio
Copy link
Author

@Andrew-Chen-Wang Thanks for your answer. But it still works well when using django.core.cache.backends.redis.RedisCache instead of django-redis, and I just need to mute that warning, right?

@Andrew-Chen-Wang
Copy link
Collaborator

correct please simply mute for now. Thanks (just don't have much time nowadays, but will get back into it when i can!)

@vuphan-agilityio
Copy link
Author

Many thanks, @Andrew-Chen-Wang 👍 Awesome lib!

f213 added a commit to tough-dev-school/education-backend that referenced this issue Mar 7, 2023
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

Successfully merging a pull request may close this issue.

2 participants