#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):
For cases 2, 3 and 5, if someone has a custom `TEST_RUNNER` set, the
changed default test runner has no impact on them, so there is no point in
warning. Any changes they will ever see will be due to their own changes
to the `TEST_RUNNER` setting, not due to upgrading Django. So I think the
handling there is correct.
That leaves case 4. Basically I think we need a setting like the one shai
mentions in order to handle this correctly, if the "check" command is
intended to be something that you can run anytime and should give you a
clean slate. When this check was added, the check command was envisioned
as something you'd run once at upgrade time that would alert you to
anything you might need to know about, so false alarms on fresh 1.6
projects were not considered a big problem.
--
Ticket URL: <https://code.djangoproject.com/ticket/21197#comment:2>
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.507c7a720065be89e0675c62b943c456%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
