#23899: A new field/doc note in the settings.py to denote django version
-------------------------------------+-------------------------------------
     Reporter:  atmb4u               |                    Owner:  nobody
         Type:  New feature          |                   Status:  new
    Component:  Core (Other)         |                  Version:  master
     Severity:  Normal               |               Resolution:
     Keywords:  settings.py, django  |             Triage Stage:  Accepted
  version                            |      Needs documentation:  0
    Has patch:  0                    |  Patch needs improvement:  0
  Needs tests:  0                    |                    UI/UX:  0
Easy pickings:  1                    |
-------------------------------------+-------------------------------------

Comment (by carljm):

 Hi Russ - I'm not convinced that we should try to use a settings file
 marker of any kind for that upgrade-checks purpose, because you still end
 up with too many false positives ("yes, my project settings were initially
 generated on 1.5, and yes I'm running 1.6, and yes I don't have
 TEST_RUNNER set, and yes, my tests are still just fine, thanks for
 asking"). My proposal here was really geared towards "possibly
 informational for readers, but not intended for machine parsing at all" --
 if we're going to bother with machine parsing a comment, why not just make
 it a setting?

 With the sort of "generated by" comment I'm suggesting here, I'd expect at
 least advanced users - myself included - to just remove it once they go
 through their settings file and edit it sufficiently that it's now more
 "written by me" than "generated by Django". So I wouldn't consider it
 something whose presence Django should rely on.

 (It's somewhat off-topic for this ticket, but my current feeling about
 upgrade checks is that we just simply shouldn't add them at all. People
 who upgrade without bothering to even read the backwards-incompatible-
 changes section of the release notes make their own bed, they can lie in
 it. Checks should only be loud about things that we can confidently say
 are a configuration problem given what we know about the current state,
 not what we try to infer about whether they might have recently upgraded.)

--
Ticket URL: <https://code.djangoproject.com/ticket/23899#comment:4>
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 post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.c033696ea7be28bcc2c268a014552df4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to