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 vitaly
Recipients Denis.Bilenko, hynek, ned.deily, neologix, ronaldoussoren, vitaly
Date 2012-09-11.15:52:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1347378772.36.0.335567578428.issue15896@psf.upfronthosting.co.za>
In-reply-to
Content
> What's wrong with working around this bug by reading a smaller amount? How much data is there supposed to be?

This makes sense for working around the issue.  Even in the blocking-read case, such as in subprocess.Popen, attempting to read a 1MB chunk of data in a single os.read call is unhelpful anyway - see http://bugs.python.org/issue15918.  Also, the 1MB read forces os.read() to unnecessarily allocate a huge !MB buffer (even if only for a short lifetime)
History
Date User Action Args
2012-09-11 15:52:52vitalysetrecipients: + vitaly, ronaldoussoren, ned.deily, neologix, hynek, Denis.Bilenko
2012-09-11 15:52:52vitalysetmessageid: <1347378772.36.0.335567578428.issue15896@psf.upfronthosting.co.za>
2012-09-11 15:52:51vitalylinkissue15896 messages
2012-09-11 15:52:51vitalycreate