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 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 <>
> 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()?
Date User Action Args
2015-03-25 19:56:08akirasetrecipients: + 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:08akirasetmessageid: <>
2015-03-25 19:56:08akiralinkissue1191964 messages
2015-03-25 19:56:08akiracreate