From 44046e8a38225067d4d0feac35367eeae133446a Mon Sep 17 00:00:00 2001 From: Preston Holmes Date: Fri, 16 Nov 2012 16:50:50 -0800 Subject: Fixed #18985 -- made DeprecationWarnings loud Capture warnings in Python >= 2.7 and route through console handler, which is subject to DEBUG==True Thanks to dstufft for the idea, and claudep for initial patch --- docs/releases/1.5.txt | 7 +++++++ 1 file changed, 7 insertions(+) (limited to 'docs') diff --git a/docs/releases/1.5.txt b/docs/releases/1.5.txt index 8b7af2cf36..c53518feaa 100644 --- a/docs/releases/1.5.txt +++ b/docs/releases/1.5.txt @@ -306,6 +306,13 @@ Django 1.5 also includes several smaller improvements worth noting: :attr:`~django.db.models.Options.index_together` documentation for more information. +* During Django's logging configuration verbose Deprecation warnings are + enabled and warnings are captured into the logging system. Logged warnings + are routed through the ``console`` logging handler, which by default requires + :setting:`DEBUG` to be True for output to be generated. The result is that + DeprecationWarnings should be printed to the console in development + environments the way they have been in Python versions < 2.7. + Backwards incompatible changes in 1.5 ===================================== -- cgit v1.3