--
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 django-develop...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/bdb84d20-0489-4ecd-b198-fa5878f5c617%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
How about making one of the third-party packages an optional dependency? Celery, for example, does that: you can just install celery[redis] without having to figure out what other packages you need to enable redis support.Ivan.
On Wed, Jun 19, 2019 at 6:44 AM Josh Smeaton <josh....@gmail.com> wrote:
There are already several 3rd party packages that implement redis as a django cache backend, for example https://github.com/niwinz/django-redis--We already have a base class for cache backends - and several implementing it (such as memcache). I don't think there's much benefit taking on another backend when it's already got very good support as an external package.
On Tuesday, 18 June 2019 01:14:25 UTC+10, Dulmandakh Sukhbaatar wrote:Hello,I would like to work on Redis support in core, and I would like to discuss proper solution for that.Redis is getting so popular and almost every modern backend stack uses it someway, therefore I think that supporting it as a cache backend in core would make Django more appealing. A solution I'm proposing is to extract base KV backend from current Memcached and extend it for both Memcached and Redis, and this won't add many new code to the core. Also we'll have base class for KV storage backends.Thanks.
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 django-d...@googlegroups.com.
--
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 django-develop...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/3a506133-f08a-4d25-a9c5-099aae3722d8%40googlegroups.com.
I’m also +1 on having it as part of core given how prominent Redis is.
I agree with Aymeric that it shouldn’t be Django’s responsibility to provide or wrap advanced Redis functionalities but I think it would be lovely if we at least exposed the connection/client as a public API.
Regards,
Loïc
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/F93AED93-32FC-4BF4-BDA7-48B4A76A8314%40polytechnique.org.
To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/335b087c-801a-452b-a5b3-a9711e4a00b8%40googlegroups.com.
> > To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/335b087c-801a-452b-a5b3-a9711e4a00b8%40googlegroups.com <https://groups.google.com/d/msgid/django-developers/335b087c-801a-452b-a5b3-a9711e4a00b8%40googlegroups.com?utm_medium=email&utm_source=footer>.
> > For more options, visit https://groups.google.com/d/optout.
>
> --
> 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 django-d...@googlegroups.com.
> To post to this group, send email to
> django-d...@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-developers.
> To view this discussion on the web visit
To move this forwards, my suggestion would be to write a DEP, to flesh out the rationale for a built-in solution, and to focus on the breadth of functionality the built-in backend would support. My preference would be a basic set of features, like the other cache backends. I believe that's what django-redis-cache does. This will leave room for third-party packages like django-redis to provide more advanced features. To give a concrete example, like other cache and database backends, a redis backend could provide persistent connections but not implement a connection pool. Until now Django has left the management of connection pools to third-party packages.
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: django-d...@googlegroups.com [mailto:django-d...@googlegroups.com]
On Behalf Of Jacob Rief
Sent: Thursday, September 5, 2019 1:33 AM
To: django-d...@googlegroups.com
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.
--
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
django-develop...@googlegroups.com.
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/b9357775f9684aa888091bce83f2852b%40iss2.ISS.LOCAL.
Just as a "new" user of Django channels/Redis:
to install/setup Redis was one of the big obstacles in my mind that kept me from using channels until now. It's not that it would be complicated to install - I just have a "knot in my thoughts" when trying to create a simple channels app and used days of investigation on "isn't that possible to use channels without the redis server setup? Can't I just install django and django-channels and go for it, at least for development?"
Maybe it's easier as I thought, but adding that as a core feature would be a big benefit IMHO.
If I understood all correctly.
Greets, Christian
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/10675445-9101-4F5A-8151-A105B939E482%40tomforb.es.
-- Dr. Christian González https://nerdocs.at
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/b9357775f9684aa888091bce83f2852b%40iss2.ISS.LOCAL.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CANE-7mU9m23CWkGrvEETxOhyCFTsU-uP1dS0qnn%3DvPXfemTdqg%40mail.gmail.com.
To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/0e71e262-d7d6-4323-af64-359eada8c8fc%40googlegroups.com.