Message90294
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. |
|
Date |
User |
Action |
Args |
2009-07-08 23:19:08 | srid | set | recipients:
+ srid, vinay.sajip |
2009-07-08 23:19:08 | srid | set | messageid: <1247095148.7.0.63830251108.issue6333@psf.upfronthosting.co.za> |
2009-07-08 23:19:07 | srid | link | issue6333 messages |
2009-07-08 23:19:07 | srid | create | |
|