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 srid
Recipients srid, vinay.sajip
Date 2009-07-08.23:19:07
SpamBayes Score 6.185372e-05
Marked as misclassified No
Message-id <1247095148.7.0.63830251108.issue6333@psf.upfronthosting.co.za>
In-reply-to
Content
Perhaps there is an issue with py.test.

My understanding is that: if the logging module is designed to let 
users implement their own custom handlers (like I did with 
ConsoleHandler), is it not expected that they may do whatever they want 
with it including closing the file (in this case - sys.stdout is a 
temporary file that is obviously closed at one stage)? Shouldn't the 
logging module be reliable in such cases?

I will point holger (author of py.test) to this issue in case if he has 
any comments.

Anyways, this is a very low-prio bug for me .. especially when there is 
a workaround.
History
Date User Action Args
2009-07-08 23:19:08sridsetrecipients: + srid, vinay.sajip
2009-07-08 23:19:08sridsetmessageid: <1247095148.7.0.63830251108.issue6333@psf.upfronthosting.co.za>
2009-07-08 23:19:07sridlinkissue6333 messages
2009-07-08 23:19:07sridcreate