Re: GSOC Proposal: Adding Redis Cache Backend To Django Core.

[Carlton Gibson]

Hi Girish, Welcome. 

Have a search of the history of the mailing list here. There was one, or a 
couple of (?) threads on adding a Redis backend recently (last year or 
two). 

>From the "Why Redis" section of your proposal, I think the answer is simply 
that lots of users (most in fact according the recent survey) are using 
Redis for caching, and we a should have a backend in core for that. 

The scope is JUST to satisfy the cache backend API, and no more. It's a 
non-goal to deal with any other Redis features, so various data structures 
and such is not relevant. (Third-party packages would could offer things in 
this space.) 

For the work breakdown compare the recent PR adding the pymemcache backend. 
#29887  — the project would be 
similar in scope.

The ground here is well-trodden, so most of it is documentation — we need 
to be very clear on requirements, installation and setup. 

I hope that helps. 

Kind Regards,

Carlton



On Monday, 29 March 2021 at 16:30:29 UTC+2 girishs...@gmail.com wrote:

> Hello, I am Girish Sontakke from India. I am willing to start contributing 
> to Django through GSOC 2021. I have gone through the Idea List available on 
> the Django wiki page for GSOC 
>  and select the 
> project of adding Redis Cache Backend To Django Core. For this, I have 
> explored the django.core.cache 
>  section of 
> the framework and take some Ideas for Django's Cache Framework 
>  from the 
> documentation available at djangoprojects.com.
> There are some caching backends already available in the django core but 
> Redis being one the popular caching engines, there should be the 
> implementation of Redis Backend in the core django package.  There are some 
> Greate packages out there for integrating Redis into Django such as 
> django-redis  and 
> django-redis-cache , 
> still, there is a need for inner Redis Backend in django.
> For this I am writing a proposal here 
> . 
> I request all of the fellow developers and mentors to give some suggestions 
> for this Idea and share your views on this project.
>  
> With Regards, 
> Girish Sontakke.
>

-- 
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-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/6b67c2aa-cd90-46ed-a1ee-72bacd9e332bn%40googlegroups.com.

Re: GSOC Proposal: Adding Redis Cache Backend To Django Core.

[Girish Sontakke]

Thank you, Carlton,
I search for discussion in the mailing list about Redis cache I found a 
helpful discussion here. 
 
Should 
I put my proposal there or should I continue here?

In the "Why Redis" section of my proposal, I have mentioned about the 
different data structures provided by Redis because I thought It is 
important with respect to the speed and efficiency of Redis cache backend 
compared to other backends like filesystem and database cache backends 
which eventually leads to its popularity. I will add the point about the 
popularity of redis among the developer community.

I have gone through the PR #13310 
, proposing the patch for 
adding support for pymemcache in the Django core, as suggested by you at 
the forum discussion 

.

Now I have doubt that whether I should remove *Provides Many 
Data-Structures *point from the "Why Redis" section or keep it there?.

That helped me a lot.

With Regards,
Girish
On Wednesday, March 31, 2021 at 1:01:59 PM UTC+5:30 carlton...@gmail.com 
wrote:

> Hi Girish, Welcome. 
>
> Have a search of the history of the mailing list here. There was one, or a 
> couple of (?) threads on adding a Redis backend recently (last year or 
> two). 
>
> From the "Why Redis" section of your proposal, I think the answer is 
> simply that lots of users (most in fact according the recent survey) are 
> using Redis for caching, and we a should have a backend in core for that. 
>
> The scope is JUST to satisfy the cache backend API, and no more. It's a 
> non-goal to deal with any other Redis features, so various data structures 
> and such is not relevant. (Third-party packages would could offer things in 
> this space.) 
>
> For the work breakdown compare the recent PR adding the pymemcache 
> backend. #29887  — the 
> project would be similar in scope.
>
> The ground here is well-trodden, so most of it is documentation — we need 
> to be very clear on requirements, installation and setup. 
>
> I hope that helps. 
>
> Kind Regards,
>
> Carlton
>
>
>
> On Monday, 29 March 2021 at 16:30:29 UTC+2 girishs...@gmail.com wrote:
>
>> Hello, I am Girish Sontakke from India. I am willing to start 
>> contributing to Django through GSOC 2021. I have gone through the Idea List 
>> available on the Django wiki page for GSOC 
>>  and select the 
>> project of adding Redis Cache Backend To Django Core. For this, I have 
>> explored the django.core.cache 
>>  section 
>> of the framework and take some Ideas for Django's Cache Framework 
>>  from the 
>> documentation available at djangoprojects.com.
>> There are some caching backends already available in the django core but 
>> Redis being one the popular caching engines, there should be the 
>> implementation of Redis Backend in the core django package.  There are some 
>> Greate packages out there for integrating Redis into Django such as 
>> django-redis  and 
>> django-redis-cache , 
>> still, there is a need for inner Redis Backend in django.
>> For this I am writing a proposal here 
>> . 
>> I request all of the fellow developers and mentors to give some suggestions 
>> for this Idea and share your views on this project.
>>  
>> With Regards, 
>> Girish Sontakke.
>>
>

-- 
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-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/b46dcb48-fec4-4bf8-b71e-cb40cd03a6d3n%40googlegroups.com.

Re: Request for Comment: settings growth configuring Email Backend.

[Tim Graham]

I don't think settings create any harm. They seem cleaner than suggesting 
subclassing the backend. If I'm understanding correctly, that would force 
everyone to write something like:

class MySMTPBackend(smtp.EmailBackend)
def __init__(self, *args, **kwargs):
super().__init__(*args, keyfile='', **kwargs)

That sort of code probably isn't suitable for `settings.py` itself which 
means configuration data like `''` is scattered elsewhere, or 
else developers are forced to write boilerplate and create their own 
settings to refer to `''`.

See also past discussion "Move SMTP / email settings to a dictionary" 
(wontfix)
https://code.djangoproject.com/ticket/22734
On Thursday, November 26, 2020 at 5:03:19 AM UTC-5 carlton...@gmail.com 
wrote:

> Hi Michiel.
>
>
> On 25 Nov 2020, at 17:53, Michiel Beijen  wrote:
>
> the old ones should be marked deprecated and
> probably should have been marked as such some Django releases ago.
>
>
> There you are, super. 👍
>
> Thank you for your input! 
>
> Kind Regards,
>
> Carlton
>
>
>
>
>

-- 
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-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/5223f927-f30b-40f7-bba0-a7c2f30e6a28n%40googlegroups.com.

Re: GSOC Proposal: Adding Redis Cache Backend To Django Core.

[Carlton Gibson]

> On 31 Mar 2021, at 11:00, Girish Sontakke  wrote:
> 
> Now I have doubt that whether I should remove Provides Many Data-Structures 
> point from the "Why Redis" section or keep it there?.

I don’t think it’s vital either way… but it seems a distraction. That Redis has 
HyperLogLog isn’t something that will matter at all to the cache backend. 

I’d try to focus on the details of the implementation: Look at the backend API, 
set(), get() &co. Look at the two existing third-party backend, and see what 
they do there. 

I’d also think about getting the documentation right — there are a few options 
with installs and connections and … — you don’t have to solve all of those in 
the proposal but showing that you’re aware of them would be good.

I hope that helps. 

Kind Regards,

Carlton

-- 
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-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/35E1DF6B-82C5-48FE-8D58-4C4BBD350671%40gmail.com.

GSOC Proposal : Adding a Redis cache backend to Core

[Daniyal Abbasi]

Hey
I am an aspirant  for GSOC 2021. I was really interested in the project
"Adding a Redis cache backend to Core" as I myself have used third party
libraries to integrate redis as a caching backend. A link to by draft
proposal can be found here
.
I have shared this draft proposal to the gsoc dashboard too.

Regards,
Daniyal Abbasi

-- 
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-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAHcKF3FA0xSy_APOKbn_5PP1bR14aAx-NS8vd8YgawKNkZJNng%40mail.gmail.com.