This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author r.david.murray
Recipients r.david.murray
Date 2015-06-01.19:15:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In my test framework I have a 'verbose' flag that causes the logging output to be written to the console[*], which helps greatly during debugging.  However, if assertLogs is used, the logging is suppressed, and when debugging logging failures it is really helpful to see the full logging output :).

Ideally there would be a unittest-supported 'verbose' flag that assertLogs could look at and not suppress existing logging when it is at level 2 or greater.  Or perhaps a flag specific to logging output would be better?  I don't really care what the API is as long as I can arrange to set it from the CLI as part of running individual tests.
Date User Action Args
2015-06-01 19:15:30r.david.murraysetrecipients: + r.david.murray
2015-06-01 19:15:30r.david.murraysetmessageid: <>
2015-06-01 19:15:30r.david.murraylinkissue24352 messages
2015-06-01 19:15:30r.david.murraycreate