Message170316
| 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) |
|