Django: Email Backend Overhaul and Admin Actions
Django merged six pull requests on May 13th, implementing a major email backend configuration system and adding admin actions to change forms. Additional fixes addressed deprecation warnings, UI text, and development environment issues.
Duration: PT1M45S
Transcript
Good morning, this is your Django development briefing for May 14th, 2026.
Mike Edmunds merged the implementation of dictionary-based MAILERS, a significant change that aligns Django's email backend configuration with other framework components like caches and databases. The new system introduces a MAILERS setting, deprecates the existing EMAIL_BACKEND configuration, and adds a `using` argument to mail sending APIs. This follows Django Enhancement Proposal 18 and represents over 3,500 lines of changes across 47 files.
Marcelo Galigniana merged support for admin actions on edit pages, addressing a 14-year-old feature request. Admin actions are now available in both list and detail views, with updated CSS and templates to support the interface changes.
Jacob Walls merged three smaller fixes: adding missing deprecation warnings for USE_BLANK_CHOICE_DASH setting, replacing "Go" with "Run" in list editable alert messages to fix a recent UI inconsistency, and removing a workaround for a CPython minidom vulnerability that has been patched upstream.
VAIBHAVPANT07 merged a fix for tox configuration on Darwin ARM64 systems, adding environment variables for dynamically linked binaries like GDAL and GEOS that Homebrew installs in non-standard paths.
What's next: The email backend changes represent a major architectural shift that will require migration planning for existing projects. The admin actions enhancement brings long-requested functionality that should improve workflow efficiency for Django administrators.
That's your Django briefing. Stay informed, keep coding.