Erik Demaine <edema...@mit.edu> added the comment:

I just tested on Python 2.5.2, 2.6.2, and 3.0.1, and I could not reproduce the 
error (using the code in msg28537).  It would seem that file.flush is catching 
the problem, even though file.write is ignoring the error, but I can't see any 
changes since 1.5.2 that would have changed this behavior of file.flush.  So 
I'm not sure what happened, but at least it seems to no longer be a bug.  
Closing.

----------
status: pending -> closed

_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue1488934>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to