summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorClaude Paroz <claude@2xlibre.net>2014-04-12 15:31:37 +0200
committerClaude Paroz <claude@2xlibre.net>2014-04-12 15:35:11 +0200
commita6eda3a5fc524333b476deed5057ee9803d91108 (patch)
treec0b477f8bc79209c32274845e8025b453d93d47a /docs
parentd9f8cc12aeeb5309139a79d9b613fa405ebed36e (diff)
[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.
Diffstat (limited to 'docs')
-rw-r--r--docs/topics/testing/tools.txt5
1 files changed, 5 insertions, 0 deletions
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`