New submission from tholzer <thol...@wetafx.co.nz>: When printing to a closed stdout file descriptor, the print statement only raises an IOError at character 8192.
The expected behaviour is that IOError gets raised immediately (i.e. on the first character). Compare this behaviour to writing to a closed sys.stderr. To reproduce (using bash): <pre> # python -V Python 2.6.4 # python -c 'print "x" * 8191' 1>&- ; echo $? close failed in file object destructor: Error in sys.excepthook: Original exception was: 0 # python -c 'print "x" * 8192' 1>&- ; echo $? Traceback (most recent call last): File "<string>", line 1, in <module> IOError: [Errno 9] Bad file descriptor 1 </pre> ---------- components: Interpreter Core messages: 99351 nosy: tholzer severity: normal status: open title: print statement delayed IOError when stdout has been closed type: behavior versions: Python 2.6 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue7932> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
