#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 Ronny Vedrilla):
@Tim: You are right and we talked about that. But since maintenance is a
huge thing in a softwares lifecycle, all the help you can get is a huge
plus IMHO.
Therefore I argue in favour of somehow "disencouraging" variables that
were already used by the framework. If someone really insists on naming a
variable this way (why should you have such a strong opinion about it?),
you can still disable the check, right?
--
Ticket URL: <https://code.djangoproject.com/ticket/35674#comment:11>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070192477dc0de-c1a63349-3fa4-4994-ada3-40da13db139d-000000%40eu-central-1.amazonses.com.
