9👍
It looks like the developers have decided to remove this warning:
45👍
Found a blog post that reveals explicitly specifying
TEST_RUNNER = 'django.test.runner.DiscoverRunner'
in settings.py
will stop this warning from occurring.
- [Django]-Get protocol + host name from URL
- [Django]-OSError: [Errno 18] Invalid cross-device link
- [Django]-How to write a unit test for a django view?
10👍
See https://github.com/django/django/blob/1.7/django/core/checks/compatibility/django_1_6_0.py#L42 for the list of things it checks that gives you this error.
- [Django]-Django post_save preventing recursion without overriding model save()
- [Django]-How can I create custom page for django admin?
- [Django]-110: Connection timed out (Nginx/Gunicorn)
9👍
You can silence individual system check warnings with the SILENCED_SYSTEM_CHECKS setting.
Regarding your other question about how to find the reasons why this warning was triggered, the only place I could find was by looking at the source code.
- [Django]-Passing STATIC_URL to file javascript with django
- [Django]-How to pass multiple values for a single URL parameter?
- [Django]-Django admin make a field read-only when modifying obj but required when adding new obj
8👍
If everything’s OK with your tests, you can simply turn the warning off by doing one (or all) of these steps:
-
Remove
SITE_ID
from your settings if you don’t use sites framework anymore. -
Add
BASE_DIR
variable to your settings. -
Remove
MANAGERS
list form your setting if you don’t use it. -
Remove
XFrameOptionsMiddleware
middleware in settings. (It’s enabled by default in Django 1.6+ anyway) -
Remove custom
TEMPLATE_LOADERS
orADMINS
if you don’t need them (you usually do, so don’t do it unless you know what you’re doing).
Those are two things current heuristics (Django 1.7.3) checks in order to detect if your project was generated by Django <1.6.
- [Django]-Django: How to pre-populate FormView with dynamic (non-model) data?
- [Django]-Restrict django FloatField to 2 decimal places
- [Django]-Mac OS X – EnvironmentError: mysql_config not found