Message239280
| Author |
akira |
| 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 |
2015年03月25日.19:56:08 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1427313368.37.0.616039602945.issue1191964@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
> I'm going to be honest; seeing None being returned from a pipe read feels *really* broken to me. When I get None returned from an IO read operation, my first instinct is "there can't be anything else coming, why else would it return None?"
It is how it is done in similar cases (returning `None` to indicate
"would block"). Do you know a better method that would allow to
distinguish between EOF (no future data, ever) and "would block"
(future data possible) without calling process.poll()? |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2015年03月25日 19:56:08 | akira | set | recipients:
+ akira, gvanrossum, josiahcarlson, astrand, parameter, vstinner, techtonik, giampaolo.rodola, ajaksu2, ooooooooo, v+python, r.david.murray, cvrebert, ericpruitt, Andrew.Boettcher, rosslagerwall, sbt, martin.panter, janzert, yselivanov, eryksun |
| 2015年03月25日 19:56:08 | akira | set | messageid: <1427313368.37.0.616039602945.issue1191964@psf.upfronthosting.co.za> |
| 2015年03月25日 19:56:08 | akira | link | issue1191964 messages |
| 2015年03月25日 19:56:08 | akira | create |
|