Author: aaugustin Date: 2012-02-27 14:52:07 -0800 (Mon, 27 Feb 2012) New Revision: 17597
Modified: django/trunk/docs/topics/testing.txt Log: Clarified the fact that the signal_changed signal isn't used by Django itself (yet). Refs #17787. Modified: django/trunk/docs/topics/testing.txt =================================================================== --- django/trunk/docs/topics/testing.txt 2012-02-27 21:15:25 UTC (rev 17596) +++ django/trunk/docs/topics/testing.txt 2012-02-27 22:52:07 UTC (rev 17597) @@ -1477,11 +1477,13 @@ .. note:: - When overriding settings make sure to also handle the cases in which - Django or your app's code uses a cache or similar feature that retains - state even if the setting is changed. Django provides the - :data:`django.test.signals.setting_changed` signal to connect cleanup - and other state-resetting callbacks to. + When overriding settings make sure to also handle the cases in which your + app's code uses a cache or similar feature that retains state even if the + setting is changed. Django provides the + :data:`django.test.signals.setting_changed` signal to connect cleanup and + 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 ~~~~~~~~~~~~~~~~~~~~~~~~ -- You received this message because you are subscribed to the Google Groups "Django updates" group. To post to this group, send email to django-updates@googlegroups.com. To unsubscribe from this group, send email to django-updates+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-updates?hl=en.
