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

This removes the need to load django.test when not testing.
This commit is contained in:
Collin Anderson 2014-10-09 11:46:40 -04:00 committed by Tim Graham
parent c5c235cd4f
commit 5dddd79433
6 changed files with 15 additions and 4 deletions

View file

@ -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``

View file

@ -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
^^^^^^^^^^^^^^^^^^^^^^