$ the-wire · showcase
Address objects gain first-class support in email settings
By RepoJournal · Filed · About Django · Composed from the cited sources · methodology
3 people shipped this
Django's email stack now accepts email.headerregistry.Address objects in ADMINS and MANAGERS, the same objects it already accepted for DEFAULT_FROM_EMAIL, SERVER_EMAIL, and the send_* helpers, closing the last place where a display name built from variable parts had to be flattened into a string.
Fixed #37167 -- Allowed email.headerregistry.Address objects as email addresses. django/django
ADMINS and MANAGERS used to reject non-string values, so an Address could not be used there even though it is the safe way to build an address with a display name from variable parts. The support already present in DEFAULT_FROM_EMAIL, SERVER_EMAIL, send_mail(), send_mass_mail(), and EmailMessage is now documented and tested for those two settings as well.
Fixed #37167 -- Allowed Address objects as email addresses. django/django
The email counterpart to the settings change: _send_server_message() now takes Address objects for ADMINS and MANAGERS, and unnecessary string casting was removed from EmailMessage so Python's own header handling is left to do the work.
Fixed #37212 -- Improved djangodocs Sphinx extension portability. django/django
The djangodocs Sphinx extension drops its table and parameterlist customizations in DjangoHTMLTranslator, which existed to strip html4-era output that Sphinx's html5 writer has not emitted since Sphinx 2.0. The removed overrides relied on Sphinx internals that shift between releases, so the extension should break less often on Sphinx upgrades.
Fixed #37212 -- Improved djangodocs Sphinx extension compatibility. django/django
Same portability effort, other half: the extension sheds fragile workarounds for ancient Docutils behavior and decouples the console-tabs implementation in the extension from the custom djangodocs theme.
:tractor: Confirmed sponsorship inquiries on their own page django/djangoproject.com
A plan inquiry used to land on the Foundation's generic "Message sent" page; it now goes to /sponsor/plans/<slug>/sent/, which names the tier and says who picks it up. The inquiry email names the plan and amount and sets a Reply-To, so the fundraising team can answer without digging the address out of the message.
Clarified "Documenting new features" in "Writing Documentation" page. django/django
Two smaller doc-side changes: the "Documenting new features" section of the Writing Documentation page was clarified, and django/django-asv added results for ubuntu-latest.
