1👍
It’s happening because the django.utils.importlib
module is removed in Django 1.9, in favor of the importlib
in the standard library. Django Rest Framework still uses it.
You can disable the warning by following the instructions on the accepted answer of this question — How to suppress the deprecation warnings in Django?
- [Answered ]-Can't get AJAX POST working in Django
- [Answered ]-How to write get and post test methods for views in django?
- [Answered ]-Why is django form is updating user object even when the validation fails
- [Answered ]-Django drf login template
- [Answered ]-Django 1.9 migrate for the first time is not creating tables
0👍
If you just want to silence the warning in mod_wsgi
, you may add a configuration directive such as:
WSGIPythonWarnings ignore::DeprecationWarning::
See this blog entry, the release notes (point 15) and the original issue.
In essence, mod_wsgi had no equivalent to the -W
control option, so a directive was added. The default must have been kept at “log everything” to be consistent across different wsgi apps.
- [Answered ]-Importing classes from another app in Django
- [Answered ]-How to override Django-CMS templates
- [Answered ]-Control consume speed of celery worker
Source:stackexchange.com