Skip to content

[pull] main from django:main#407

Merged
pull[bot] merged 2 commits intothreatcode:mainfrom
django:main
May 8, 2026
Merged

[pull] main from django:main#407
pull[bot] merged 2 commits intothreatcode:mainfrom
django:main

Conversation

@pull
Copy link
Copy Markdown

@pull pull Bot commented May 8, 2026

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

medmunds added 2 commits May 8, 2026 08:41
Replaced the (currently unused) LazySettings._show_deprecation_warning()
with a module-level _show_settings_deprecation_warning() function.

The new function can be called from any settings-related code, not just
LazySettings methods. It correctly distinguishes internal from external
settings usage when override_settings() is involved.
Reworked tests/mail/test_backends.py so that cases covering functional
behavior don't depend on EMAIL_BACKEND or other EMAIL_* settings. (But
kept unchanged existing tests to verify backend instance properties are
initialized from EMAIL_* settings.)

Most backend behavior tests had implicitly relied on email settings
overrides in test setup (e.g., to use an emulated SMTP server). They
either used mail.get_connection(...) or directly constructed a backend
class instance with the specific attributes being tested, relying on
the settings overrides to initialize other required attributes. That
approach won't work after those settings are deprecated as part of
EMAIL_PROVIDERS.

Instead, replaced backend construction in "functional" tests with new
SharedEmailBackendTests.create_backend() which constructs the testable
backend instance with _all_ options needed to avoid global settings.

Tests to verify the settings are read correctly continue to directly
construct backend instances, without using create_backend().
@pull pull Bot locked and limited conversation to collaborators May 8, 2026
@pull pull Bot added the ⤵️ pull label May 8, 2026
@pull pull Bot merged commit 3e0190a into threatcode:main May 8, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant