Fixed #20349 -- Moved setting_changed signal to django.core.signals.

This removes the need to load django.test when not testing.

2 files changed, 11 insertions, 0 deletions

diff --git a/docs/ref/signals.txt b/docs/ref/signals.txt
index b41b3f63dd..84bb7f570e 100644
--- a/docs/ref/signals.txt
+++ b/docs/ref/signals.txt
@@ -666,6 +666,13 @@ It's actually sent twice: when the new value is applied ("setup") and when the
 original value is restored ("teardown"). Use the ``enter`` argument to
 distinguish between the two.
 
+You can also import this signal from ``django.core.signals`` to avoid importing
+from ``django.test`` in non-test situations.
+
+.. versionchanged:: 1.8
+
+    The signal was moved to ``django.core.signals`` as described above.
+
 Arguments sent with this signal:
 
 ``sender``
diff --git a/docs/releases/1.8.txt b/docs/releases/1.8.txt
index e2cb8cd2ff..26fc2c17a2 100644
--- a/docs/releases/1.8.txt
+++ b/docs/releases/1.8.txt
@@ -460,6 +460,10 @@ Signals
   the request, was added to the :data:`~django.core.signals.request_started`
   signal.
 
+* You can now import the :func:`~django.test.signals.setting_changed` signal
+  from ``django.core.signals`` to avoid loading ``django.test`` in non-test
+  situations. Django no longer does so itself.
+
 System Check Framework
 ^^^^^^^^^^^^^^^^^^^^^^