#35674: Provide a check for settings removed (post deprecation)
-------------------------------------+-------------------------------------
Reporter: Serafeim | Owner: (none)
Papastefanos |
Type: New feature | Status: new
Component: Core (System | Version: 5.1
checks) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Adam Johnson):
I did a quick grep for `setting.*removed` in `docs/releases` and found the
below. It’s likely incomplete but a good starting place. I think we
shouldn’t have a cut off and should feature all these settings in the
check. Projects can be very long-lived...
5.1
* `DEFAULT_FILE_STORAGE`
* `STATICFILES_STORAGE`
5.0
* `DATABASES->name->TEST->SERIALIZE`
* `USE_L10N`
* `USE_DEPRECATED_PYTZ`
* `CSRF_COOKIE_MASKED`
4.1
* `CSRF_COOKIE_MASKED`
4.0
* `SECURE_BROWSER_XSS_FILTER`
* `PASSWORD_RESET_TIMEOUT_DAYS`
* `DEFAULT_HASHING_ALGORITHM`
3.1
* `FILE_CHARSET`
3.0
* `DEFAULT_CONTENT_TYPE`
2.1
* `USE_ETAGS`
1.10
* `LOGOUT_URL`
* `ALLOWED_INCLUDE_ROOTS`
* `TEMPLATE_CONTEXT_PROCESSORS`
* `TEMPLATE_DEBUG`
* `TEMPLATE_DIRS`
* `TEMPLATE_LOADERS`
* `TEMPLATE_STRING_IF_INVALID`
1.8
* `SEND_BROKEN_LINK_EMAILS`
* `CACHE_MIDDLEWARE_ANONYMOUS_ONLY`
--
Ticket URL: <https://code.djangoproject.com/ticket/35674#comment:6>
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/01070191b49045f4-a79acc92-6547-4c85-96d2-2e27785903d2-000000%40eu-central-1.amazonses.com.
