[issue1596] Broken pipes should be handled better in 2.x

Changes by Terry J. Reedy : -- resolution: -> out of date status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue1596] Broken pipes should be handled better in 2.x

Changes by Matteo Bertini : -- nosy: +naufraghi ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue1596] Broken pipes should be handled better in 2.x

Changes by Sean Reifschneider <[EMAIL PROTECTED]>: -- priority: -> normal __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list

[issue1596] Broken pipes should be handled better in 2.x

Guido van Rossum added the comment: I'll entertain a patch for 2.6. For 2.5 I think this smells too much like a feature. -- nosy: +gvanrossum __ Tracker <[EMAIL PROTECTED]> __ ___

[issue1596] Broken pipes should be handled better in 2.x

New submission from Alexandre Vassalotti: I think Python 2.x should mimic, or improve on, the behavior of Py3k for handling broken pipes. That is: 1. Don't print the message "close failed: [Errno 32] Broken pipe", from filemodule.c; since this is impossible to override from Python. 2. Check s