Message223799
| Author |
vstinner |
| Recipients |
Andrew.Boettcher, ajaksu2, akira, astrand, cvrebert, ericpruitt, eryksun, giampaolo.rodola, gvanrossum, janzert, josiahcarlson, martin.panter, ooooooooo, parameter, r.david.murray, rosslagerwall, sbt, techtonik, v+python, vstinner, yselivanov |
| Date |
2014年07月23日.23:51:33 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1406159493.72.0.265844627577.issue1191964@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
> I have implemented and would continue to lean towards continuing to hide BrokenPipeError on the additional API endpoints.
FYI asyncio.Process.communicate() ignores BrokenPipeError and ConnectionResetError, whereas asyncio.Process.stdin.drain() (coroutine to wait until all bytes are written) raises a BrokenPipeError or ConnectionResetError if the child process exited. I think subprocess has the same design.
(I modified recently asyncio to ignore BrokenPipeError in communicate(), it was a bug.) |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2014年07月23日 23:51:34 | vstinner | set | recipients:
+ vstinner, gvanrossum, josiahcarlson, astrand, parameter, techtonik, giampaolo.rodola, ajaksu2, ooooooooo, v+python, r.david.murray, cvrebert, ericpruitt, akira, Andrew.Boettcher, rosslagerwall, sbt, martin.panter, janzert, yselivanov, eryksun |
| 2014年07月23日 23:51:33 | vstinner | set | messageid: <1406159493.72.0.265844627577.issue1191964@psf.upfronthosting.co.za> |
| 2014年07月23日 23:51:33 | vstinner | link | issue1191964 messages |
| 2014年07月23日 23:51:33 | vstinner | create |
|