| Age | Commit message (Collapse) | Author |
|
|
|
|
|
Thanks Carl Meyer for review.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
in request.
Thanks edevil for the report and Simon Charette for review.
|
|
|
|
|
|
Refs #20083.
|
|
Refs #21188. Now pure Python DeprecationWarning visibility should
be back to Python defaults.
|
|
|
|
This is the result of Christopher Medrela's 2013 Summer of Code project.
Thanks also to Preston Holmes, Tim Graham, Anssi Kääriäinen, Florian
Apolloner, and Alex Gaynor for review notes along the way.
Also: Fixes #8579, fixes #3055, fixes #19844.
|
|
When django.setup() (and then configure_logging) is called inside
catch_warnings, logging setup is negatively affected (notably
warnings.showwarning definition).
|
|
Thanks Aymeric Augustin for the report and the review.
|
|
|
|
|
|
Signed-off-by: Jason Myers <jason@jasonamyers.com>
|
|
|
|
|
|
|
|
|
|
Python 2.7 allows to combine several 'with' instructions.
|
|
|
|
Refs #20680.
|
|
SuspiciousOperations have been differentiated into subclasses, and
are now logged to a 'django.security.*' logger. SuspiciousOperations
that reach django.core.handlers.base.BaseHandler will now return a 400
instead of a 500.
Thanks to tiwoc for the report, and Carl Meyer and Donald Stufft
for review.
|
|
Gives much nicer errors when it fails.
|
|
This is a fix to the wrong behavior that 15c3906eeb introduced.
|
|
|
|
|
|
|