| Age | Commit message (Collapse) | Author |
|
if SECRET_KEY is accessed and not set."
This reverts commit b3cffde5559c4fa97625512d7ec41a674be26076 due to
a regression and performance concerns.
Backport of 5cc81cd9eb69f5f7a711412c02039b435c393135 from master
|
|
|
|
accessed and not set.
|
|
|
|
|
|
|
|
Python docs say, "it's usually not necessary to invoke these methods directly."
|
|
|
|
|
|
|
|
|
|
|
|
Also removed try/except/fail antipattern that hides exceptions.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Forwardport of ae1d663b7913f6da233c55409c4973248372d302
from stable/1.8.x plus more.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Thanks Carl Meyer for review.
|
|
The test was testing a use case that doesn't happen in real world
projects: developers don't assign settings at run time (and Django
explicitly doesn't support it).
|
|
TestCase decorator.
|
|
|
|
There's always a better word.
|
|
This reverts commit 66757fee7e921ad4c35e0b3f80c25e026100b31c.
Discussions have led to think that this functionality does not
bring significant benefits to justify the added complexity.
Read also discussions on ticket #22734.
|
|
This change is needed for upcoming changes where settings might be
grouped in a parent dictionary.
Thanks Tim Graham for the review.
|
|
|
|
|
|
Refs #20032, #18824. Thanks ztorstri at gmail.com for the report.
|
|
Thanks Piotr Kasprzyk for help with the patch.
|
|
|
|
|
|
It doesn't account for app configs.
Refs #21679.
|
|
|
|
|
|
|
|
Refs #19031.
|
|
Signed-off-by: Jason Myers <jason@jasonamyers.com>
|
|
|
|
When both parent and child classes are decorated with override_settings,
child class settings should take precedence.
Thanks Sephi for the report and Marc Tamlyn for the review.
|
|
|