Hi all. 

Can I ask for guidance/comments please? 

Ticket 31885 <https://code.djangoproject.com/ticket/31885> Update SMTP 
Email Backend to use an SSLContext came in for which there's a PR adding 
`EMAIL_SSL_CAFILE` &co settings 
<https://github.com/django/django/pull/13305/> to match the existing 
EMAIL_USE_SSL &co settings. 

The PR looks fine in itself. 

I do wonder about the growth on the number of settings here. 
It looks to my eye to get out of hand.  

An alternate would be subclass EmailBackend, containing your customisations 
there. 

Alternatively we might group setting better than just the `GROUP_` prefix 
(namespaces being one honking great idea). 

Alternatively, "no it's fine, don't worry". 

I mentioned similar about the growth of security headers in a previous 
thread 
<https://groups.google.com/g/django-developers/c/WJAbbwJKp30/m/9o6zOEhACAAJ>
. 
Django uses settings. Great! No problem. If they didn't exist, you'd have 
to invent them. But to what extent do we say that new settings are the way 
forward vs having people compose their code with configured components? 

(If I add the words "Technical Board" does that get extra eyes on this? 🙂)

Thanks for the 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/a49660ed-8e06-4b21-bf9f-506bbb0b0996n%40googlegroups.com.

Reply via email to