Clarified the fact that the signal_changed signal isn't used by Django itself (yet). Refs #17787.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@17597 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
ce88b57b9a
commit
2ddfcfbec6
|
@ -1477,11 +1477,13 @@ decorate the class::
|
||||||
|
|
||||||
.. note::
|
.. note::
|
||||||
|
|
||||||
When overriding settings make sure to also handle the cases in which
|
When overriding settings make sure to also handle the cases in which your
|
||||||
Django or your app's code uses a cache or similar feature that retains
|
app's code uses a cache or similar feature that retains state even if the
|
||||||
state even if the setting is changed. Django provides the
|
setting is changed. Django provides the
|
||||||
:data:`django.test.signals.setting_changed` signal to connect cleanup
|
:data:`django.test.signals.setting_changed` signal to connect cleanup and
|
||||||
and other state-resetting callbacks to.
|
other state-resetting callbacks to. Note that this signal isn't currently
|
||||||
|
used by Django itself, so changing built-in settings may not yield the
|
||||||
|
results you expect.
|
||||||
|
|
||||||
Emptying the test outbox
|
Emptying the test outbox
|
||||||
~~~~~~~~~~~~~~~~~~~~~~~~
|
~~~~~~~~~~~~~~~~~~~~~~~~
|
||||||
|
|
Loading…
Reference in New Issue