➜

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, schmir, vitaly
Date 2012-09-19.06:55:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1348037756.11.0.83305283696.issue15896@psf.upfronthosting.co.za>
In-reply-to
Content 
> The workaround should not be implemented in os.read because it is a very thin wrapper around the system call and should stay that way.

Although this issue was initially filed as "Sporadic EINVAL in nonblocking pipe os.read when forked child fails on Mac OS", the subsequent investigation revealed that this has nothing to do with a forked child failing.  Rather, it's a bug in the read() syscall on Mac OS X.  What would be a more appropriate place to work around this read() syscall bug than os.read?
History
Date User Action Args
2012-09-19 06:55:56vitalysetrecipients: + vitaly, ronaldoussoren, schmir, ned.deily, neologix, hynek, Denis.Bilenko
2012-09-19 06:55:56vitalysetmessageid: <1348037756.11.0.83305283696.issue15896@psf.upfronthosting.co.za>
2012-09-19 06:55:55vitalylinkissue15896 messages
2012-09-19 06:55:55vitalycreate