➜

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 vstinner
Recipients Arfrever, dmalcolm, martin.panter, pitrou, python-dev, rosslagerwall, serhiy.storchaka, vstinner
Date 2015-03-01.13:30:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAMpsgwa=qrgGXadbnzgv3Ene9YcAcNjPmHtCLeGxQUbHh5v4Wg@mail.gmail.com>
In-reply-to <1425201030.31.0.290282418548.issue21619@psf.upfronthosting.co.za>
Content 
Le dimanche 1 mars 2015, Serhiy Storchaka <report@bugs.python.org> a écrit :
>
> Why communicate() ignores BrokenPipeError?
>

It's more convinient. There is nothing useful you can do on pipe error in
communicate().

For __exit__, what do you want to on broken pipe error? I did't check yet:
the process always exit after __exit__?
History
Date User Action Args
2015-03-01 13:30:10vstinnersetrecipients: + vstinner, pitrou, Arfrever, dmalcolm, rosslagerwall, python-dev, martin.panter, serhiy.storchaka
2015-03-01 13:30:10vstinnerlinkissue21619 messages
2015-03-01 13:30:10vstinnercreate