#21197: 1.6 compatibility checks don't correctly validate TEST_RUNNER
-------------------------------------+-------------------------------------
Reporter: russellm | Owner: nobody
Type: Bug | Status: new
Component: Core (Management | Version:
commands) | 1.6-alpha-1
Severity: Release blocker | 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 carljm):
We can pull it out in a thread, but I don't have much more to say -
basically I think I agree with you that the upgrade checks are most useful
if they are run automatically, and that if we can add some sort of
version-checking to the new validate code, it can serve this purpose well.
I agree that settings are kind of ugly for the version check, but I am not
convinced there is another option that is better. Both "another file" and
"a database table" are, to my mind, much more intrusive additional project
cruft than another setting.
--
Ticket URL: <https://code.djangoproject.com/ticket/21197#comment:9>
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.780a873f2a35a4343cfa86f5b55b8eaa%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
