Message 170708 - Python tracker

➜

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	ronaldoussoren
Recipients	Denis.Bilenko, hynek, ned.deily, neologix, ronaldoussoren, schmir, vitaly
Date	2012-09-19.07:24:05
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1348039446.55.0.389105682633.issue15896@psf.upfronthosting.co.za>
In-reply-to

Content
How can you work around it in os.read, without knowing anything about what the file descriptor represents? Just triggering on getting on EINVAL error when calling read might trigger other problems and might even be a valid result for some file descriptors (for example for custom file systems or device files). And what kind of workaround do you propose?

How can you work around it in os.read, without knowing anything about what the file descriptor represents? Just triggering on getting on EINVAL error when calling read might trigger other problems and might even be a valid result for some file descriptors (for example for custom file systems or device files).

And what kind of workaround do you propose?

History
Date	User	Action	Args
2012-09-19 07:24:06	ronaldoussoren	set	recipients: + ronaldoussoren, schmir, ned.deily, neologix, hynek, vitaly, Denis.Bilenko
2012-09-19 07:24:06	ronaldoussoren	set	messageid: <1348039446.55.0.389105682633.issue15896@psf.upfronthosting.co.za>
2012-09-19 07:24:06	ronaldoussoren	link	issue15896 messages
2012-09-19 07:24:05	ronaldoussoren	create