#35514: Dictionary based EMAIL_PROVIDERS settings
-----------------------------+--------------------------------------
     Reporter:  Jacob Rief   |                    Owner:  Jacob Rief
         Type:  New feature  |                   Status:  assigned
    Component:  Core (Mail)  |                  Version:  dev
     Severity:  Normal       |               Resolution:
     Keywords:               |             Triage Stage:  Accepted
    Has patch:  0            |      Needs documentation:  0
  Needs tests:  0            |  Patch needs improvement:  0
Easy pickings:  0            |                    UI/UX:  0
-----------------------------+--------------------------------------
Comment (by Jacob Rief):

 @Mike Edmunds

 addressing your questions from June 10th, 2024

 ad 1) yes, the provider name usually will be lowercased, jsut as with
 databases, caches, etc.

 ad 2) I would prefer `send_name(provider="…"`, …)`.

 ad 3) good point, should maybe be implemented in a separate issue.

 ad 4) currently I did neither address `DEFAULT_FROM_EMAIL` nor
 `EMAIL_SUBJECT_PREFIX`.

 addressing your questions from June 25th, 2024

 first) On the sprints at DjangoCon Europe we (Natalia, Carlton, Jacob)
 brainstormed for meaningful names. The conclusion was that
 `EMAIL_PROVIDERS` was the best choice.

 second) hmm, didn't think about this yet. Currently it would behave just
 like using the setting `EMAIL_…` but moved into a dictionary based
 setting.
-- 
Ticket URL: <https://code.djangoproject.com/ticket/35514#comment:10>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070190fb77855e-9052a181-73d8-46d2-a3aa-814c4be75b20-000000%40eu-central-1.amazonses.com.

Reply via email to