#22454: Confusing message id=1_6.W001
--------------------------------------+------------------------------------
     Reporter:  pgcd                  |                    Owner:  mardini
         Type:  Cleanup/optimization  |                   Status:  closed
    Component:  Core (System checks)  |                  Version:  1.6
     Severity:  Release blocker       |               Resolution:  fixed
     Keywords:                        |             Triage Stage:  Accepted
    Has patch:  0                     |      Needs documentation:  0
  Needs tests:  0                     |  Patch needs improvement:  0
Easy pickings:  1                     |                    UI/UX:  0
--------------------------------------+------------------------------------
Changes (by mrmachine):

 * cc: real.human@… (added)


Comment:

 I get this warning in a new 1.7 project, started with `startproject` and
 with the settings module customised (added SITE_ID, because I use
 django.contrib.sites; defined TEMPLATE_LOADERS, because I use a custom
 template loader; and defined MANAGERS, because I use `mail_managers`).
 Django thinks this project has been migrated, but it hasn't. I had to
 check the source to find out why, and even the docstring says it checks if
 we have not overridden TEST_RUNNER. The link from the warning talks about
 either updating my test suite OR using a deprecated test runner to
 maintain the old behaviour. I don't need to do either, but I can force
 Django to skip this check by explicitly defining TEST_RUNNER to be the
 same value that it is already set to by default. Seems a bit of a hack.

 The linked docs should mention that Django checks a few key markers in the
 settings module to guess what version of Django you might have run in the
 past (not a very good check to begin with), and provide a new short-term
 setting specifically to disable the check if you know it doesn't apply to
 you, instead of forcing you to explicitly set the test runner to the
 default value.

 Or even better, check the markers and if they trigger then use the old
 test runner to actually detect tests that aren't found with the new runner
 and report that there "are" (instead of "may be") tests that won't run.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/22454#comment:7>
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/062.0a9b1bf6b76054dcacb8f98668f1ced1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to