#37161: Implement a system check for deprecated mail settings
-----------------------------+-------------------------------------------
     Reporter:  Jacob Walls  |                     Type:  New feature
       Status:  new          |                Component:  Core (Mail)
      Version:  6.0          |                 Severity:  Release blocker
     Keywords:               |             Triage Stage:  Unreviewed
    Has patch:  0            |      Needs documentation:  0
  Needs tests:  0            |  Patch needs improvement:  0
Easy pickings:  0            |                    UI/UX:  0
-----------------------------+-------------------------------------------
 Because the deprecated mail settings will stop working in Django 7.0, this
 could lead to data loss if someone misses the deprecation warnings and
 fails to migrate to `MAILERS`.

 For a similar scenario with `STORAGES`, on the forum we
 [https://forum.djangoproject.com/t/deprecation-of-default-file-storage-
 can-we-easen-the-migration/34284/20 appeared to agree] that in retrospect,
 we should have implemented a temporary system check in
 `core.checks.compatibility` despite some disagreement about what a more
 robust, permanent solution might look like for retiring settings.

 An example where this was implemented before is in
 354acd04af524ad82002b903df1189581c51cabe, although it's not a perfect
 analogue because that check only checked for ''conflicts'' between old &
 new settings--which we do have right now in 6.1, raising a runtime
 `ImproperlyConfigured`--not the presence of the old settings at all.

 (Interestingly, the `ImproperlyConfigured` is swallowed by `manage.py
 shell`...)

 Anyway, I think we should consider adding a system check during the
 deprecation period.
-- 
Ticket URL: <https://code.djangoproject.com/ticket/37161>
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 [email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/django-updates/0107019eb84d7488-5f299916-bc23-4d5a-b379-ffe11cf91b4d-000000%40eu-central-1.amazonses.com.

Reply via email to