[1.6.x] Fixed #22071 -- Added a warning regarding override_settings and aliasing.
Thanks EvilDMP for the suggestion. Backport of e65c0ccac0 from master
This commit is contained in:
parent
3a5da7a11c
commit
985d0865a3
@ -1104,6 +1104,10 @@ The decorator can also be applied to test case classes::
|
|||||||
the original ``LoginTestCase`` is still equally affected by the
|
the original ``LoginTestCase`` is still equally affected by the
|
||||||
decorator.
|
decorator.
|
||||||
|
|
||||||
|
Finally, avoid aliasing your settings as module-level constants as
|
||||||
|
``override_settings()`` won't work on such values since they are
|
||||||
|
only evaluated the first time the module is imported.
|
||||||
|
|
||||||
You can also simulate the absence of a setting by deleting it after settings
|
You can also simulate the absence of a setting by deleting it after settings
|
||||||
have been overriden, like this::
|
have been overriden, like this::
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user