This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author serhiy.storchaka
Recipients martin.panter, neologix, serhiy.storchaka, vstinner
Date 2015-03-03.13:17:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <8854935.NWfjJ1WFWH@raxxla>
In-reply-to <1425388436.52.0.68429347904.issue23570@psf.upfronthosting.co.za>
Content
> Your solution is different: I would prefer to also ignore broken pipe errors
> on close(). I'm not sure that close() can raise a BrokenPipeError in
> practice.

Of course all this code should be inside try/except block that ignores a 
BrokenPipeError.
History
Date User Action Args
2015-03-03 13:17:50serhiy.storchakasetrecipients: + serhiy.storchaka, vstinner, neologix, martin.panter
2015-03-03 13:17:49serhiy.storchakalinkissue23570 messages
2015-03-03 13:17:49serhiy.storchakacreate