From a6eda3a5fc524333b476deed5057ee9803d91108 Mon Sep 17 00:00:00 2001 From: Claude Paroz Date: Sat, 12 Apr 2014 15:31:37 +0200 Subject: [1.7.x] Also allowed a non-overridden setting to be deleted Refs #20032, #18824. Thanks ztorstri at gmail.com for the report. Backport of 3417ba0309 from master. --- docs/topics/testing/tools.txt | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'docs') diff --git a/docs/topics/testing/tools.txt b/docs/topics/testing/tools.txt index 25e1519c99..e176387ef2 100644 --- a/docs/topics/testing/tools.txt +++ b/docs/topics/testing/tools.txt @@ -1193,6 +1193,11 @@ have been overridden, like this:: del settings.LOGIN_URL ... +.. versionchanged:: 1.7 + + Previously, you could only simulate the deletion of a setting which was + explicitely overridden. + When overriding settings, make sure to 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` -- cgit v1.3