Message 82880 - 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	pitrou
Recipients	amaury.forgeotdarc, exarkun, gvanrossum, ocean-city, pitrou, zmedico
Date	2009-02-27.22:12:23
SpamBayes Score	0.00015368566
Marked as misclassified	No
Message-id	<1235772745.54.0.937379730335.issue5380@psf.upfronthosting.co.za>
In-reply-to

Content
Well, as I suggested, in FileIO.read(): when receiving errno=5 on a read() call and if S_IFIFO() returns true, clear errno and return an empty string. The question is whether a genuine EIO error ("low level IO error") can occur on a FIFO. Intuitively, I'd say "no" since a FIFO is only a software communication channel, but who knows...

Well, as I suggested, in FileIO.read(): when receiving errno=5 on a
read() call and if S_IFIFO() returns true, clear errno and return an
empty string.
The question is whether a genuine EIO error ("low level IO error") can
occur on a FIFO. Intuitively, I'd say "no" since a FIFO is only a
software communication channel, but who knows...

History
Date	User	Action	Args
2009-02-27 22:12:25	pitrou	set	recipients: + pitrou, gvanrossum, exarkun, amaury.forgeotdarc, ocean-city, zmedico
2009-02-27 22:12:25	pitrou	set	messageid: <1235772745.54.0.937379730335.issue5380@psf.upfronthosting.co.za>
2009-02-27 22:12:24	pitrou	link	issue5380 messages
2009-02-27 22:12:23	pitrou	create