#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):
Now, that I touched Django's mail sending code, I noticed that the current
implementation has a serious flaw: `get_connection(backend=…)` returns a
configured email backend. This means that whenever one calls this
function, the connection parameters must be provided together. The
consequence is that typical configuration settings, such as hostname,
user, password, etc. must be provided from inside the calling code, rather
that from a configuration file, aka `settings.py`. I therefore left the
`backend` parameter in `get_connection` but made it mutually exclusive
with the new parameter `provider`. In my opinion we should add a
deprecation warning whenever someone uses `backend`. What do you think?
Anyway, the current implementation from my pull request seems to work now.
I still have to add/change the documentation. Does anybody want to review
this pull request?
--
Ticket URL: <https://code.djangoproject.com/ticket/35514#comment:13>
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/01070191005419bf-72efd81e-0fac-4ceb-9560-9c972f43bb17-000000%40eu-central-1.amazonses.com.
