The django-redis maintainer is currently in the process of stepping down and is moving away from the project. Should we propose moving it to Django's GitHub? For details, see https://github.com/niwinz/django-redis/issues/400
On the other hand, if there is interest in supporting a Redis backend in core, given django-redis's status, now might be a good time to consider it. As long as memcache is in core, I'm +1 on including Redis as well. On Thu, Sep 5, 2019 at 7:40 AM Aymeric Augustin < [email protected]> wrote: > Hello, > > This is an interesting point — and one we tend to forget too often. > > The documentation for memcached says that it doesn't support Windows: > https://github.com/memcached/memcached/wiki/Install#installation > > The documentation for redis says that it supports Windows, with some > limitations, and that there's an effort by Microsoft to lift these > limitations: > > https://redislabs.com/ebook/appendix-a/a-3-installing-on-windows/a-3-1-drawbacks-of-redis-on-windows/ > > So the Windows situation seems slightly better with Redis than with > memcached, even if it isn't ideal. > > Best regards, > > -- > Aymeric. > > Le jeu. 5 sept. 2019 à 15:29, Matthew Pava <[email protected]> a > écrit : > >> I’d just like to point out that Redis support on Windows is limited at >> best. All other technologies that Django uses, as far as I can recall, do >> support Windows. >> >> >> >> *From:* [email protected] [mailto: >> [email protected]] *On Behalf Of *Jacob Rief >> *Sent:* Thursday, September 5, 2019 1:33 AM >> *To:* [email protected] >> *Subject:* Re: Redis cache support in core >> >> >> >> I'm also in favor on having it as part of the core, since memcache is >> also supported. >> >> >> >> One of the nice features Redis provides, is the possibility to invalidate >> one or more cached object by using a wildcard key. >> >> It namely is the method delete_pattern() added by django-redis-cache to >> the given Django caching backend. That >> >> (or a similar method) then should be part of the other Django caching >> backends as well, such as the dummy cache or in-memory cache. >> >> >> >> Jacob >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django developers (Contributions to Django itself)" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-developers/CAJ_HXxo9jpr-%3DFmLXcYwwR6tdn-NVDfrEoo-qYnB-vQwKv9O%3DA%40mail.gmail.com >> <https://groups.google.com/d/msgid/django-developers/CAJ_HXxo9jpr-%3DFmLXcYwwR6tdn-NVDfrEoo-qYnB-vQwKv9O%3DA%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django developers (Contributions to Django itself)" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-developers/b9357775f9684aa888091bce83f2852b%40iss2.ISS.LOCAL >> <https://groups.google.com/d/msgid/django-developers/b9357775f9684aa888091bce83f2852b%40iss2.ISS.LOCAL?utm_medium=email&utm_source=footer> >> . >> > > > -- > Aymeric. > > -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/CANE-7mU9m23CWkGrvEETxOhyCFTsU-uP1dS0qnn%3DvPXfemTdqg%40mail.gmail.com > <https://groups.google.com/d/msgid/django-developers/CANE-7mU9m23CWkGrvEETxOhyCFTsU-uP1dS0qnn%3DvPXfemTdqg%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CADhq2b4rFPmVSUHFJ2%3DMpPimzCdsRnSB%2BufgH7FSiPer6mbmAw%40mail.gmail.com.
