mirror of
https://github.com/django/django.git
synced 2025-09-26 12:09:19 +00:00
[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.
This commit is contained in:
parent
d9f8cc12ae
commit
a6eda3a5fc
3 changed files with 13 additions and 2 deletions
|
@ -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`
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue