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

2010-07-08 Thread Terry J. Reedy
Changes by Terry J. Reedy tjre...@udel.edu: -- resolution: - out of date status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1596 ___

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

2009-10-24 Thread Matteo Bertini
Changes by Matteo Bertini matt...@naufraghi.net: -- nosy: +naufraghi ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1596 ___ ___ Python-bugs-list

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

2008-03-17 Thread Sean Reifschneider
Changes by Sean Reifschneider [EMAIL PROTECTED]: -- priority: - normal __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1596 __ ___ Python-bugs-list mailing list

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

2007-12-11 Thread Alexandre Vassalotti
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

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

2007-12-11 Thread Guido van Rossum
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] http://bugs.python.org/issue1596 __