Sridhar Ratnakumar <sridh...@activestate.com> added the comment: 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. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue6333> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
