Avoid importing django.test package when not testing

Importing anything `rest_framework` causes `django.test` to be imported.
This is because DRF registers a receiver on the
`django.test_signals.setting_changed` signal.

This is not really a problem, but it is good to avoid this because it
bloats the memory with unnecessary modules (e.g. `django.test`,
`django.core.servers.basehttp`, `socketserver`) and increases the
startup time. It also doesn't feel right to import test code into
non-test code.

Try to import the signal from a core module if possible.

Note that there's another `django.test` import in `MultiPartRenderer`,
however this import is done lazily only if the functionality is used so
can be easily avoided.

Author: bluetech

rest_framework/settings.py

@@ -19,9 +19,15 @@
 back to the defaults.
 """
 from django.conf import settings
-from django.test.signals import setting_changed
 from django.utils.module_loading import import_string
 
+# Import `setting_changed` from the core package instead of its official
+# location if possible, to avoid importing the test module unnecessarily.
+try:
+    from django.core.signals import setting_changed
+except ImportError:
+    from django.test.signals import setting_changed
+
 from rest_framework import ISO_8601
 
 DEFAULTS = {