#35674: Provide a check for settings removed (post deprecation)
-------------------------------------+-------------------------------------
Reporter: Serafeim | Owner: Ronny
Papastefanos | Vedrilla
Type: New feature | Status: assigned
Component: Core (System | Version: 5.1
checks) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham):
I remain unconvinced that this is a wise change. Are we going to document
an ever growing list of
[https://docs.djangoproject.com/en/dev/topics/settings/#creating-your-own-
settings a disallowed settings names]? Disallowing something so generic as
`LOGOUT_URL` seems like it will cause unneeded annoyance.
Although the check could be disabled (usage of one disallowed setting
requires disabling the check completely), this is more of a backward-
incompatible change than a new feature.
We have had
[https://github.com/django/django/commit/6192bffb130132461e55e5fe7a7eaaa9a166d08f
temporary compatibility checks] to point out deprecated settings. I guess
that may have been more visible than a deprecation warning in the case of
`DEFAULT_FILE_STORAGE`.
--
Ticket URL: <https://code.djangoproject.com/ticket/35674#comment:19>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/010701929fa6d080-6b0420ac-e3b5-43a1-98c8-51d396e8a45c-000000%40eu-central-1.amazonses.com.
