[issue24352] Provide a way for assertLogs to optionally not hide the logging output

R. David Murray added the comment: My test harness already dumps the logging buffer on test failure. What I need this for is debugging. My test harness verbose = 2 flag turns on logging globally, and I need to see the logging from the code under test correctly interspersed with the other logg

[issue24352] Provide a way for assertLogs to optionally not hide the logging output

Robert Collins added the comment: Ok so, design thoughts here. assertLogs really does two things. Firstly it takes a copy of the logs so it can do its assertion. Secondly it disables all other logging, cleaning up noisy tests. Your specific need only conflicts with the second case. The way I

[issue24352] Provide a way for assertLogs to optionally not hide the logging output

Changes by Zachary Ware : -- nosy: +zach.ware ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyth

[issue24352] Provide a way for assertLogs to optionally not hide the logging output

Changes by Ned Deily : -- nosy: +ezio.melotti, michael.foord, rbcollins ___ Python tracker ___ ___ Python-bugs-list mailing list Unsub

[issue24352] Provide a way for assertLogs to optionally not hide the logging output

New submission from R. David Murray: 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 h