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 gvanrossum
Recipients amaury.forgeotdarc, exarkun, gvanrossum, ocean-city, pitrou, zmedico
Date 2009-02-27.22:27:51
SpamBayes Score 7.808659e-11
Marked as misclassified No
Message-id <ca471dc20902271427g4f8695cey1ae7a2fd6da616d@mail.gmail.com>
In-reply-to <1235772745.54.0.937379730335.issue5380@psf.upfronthosting.co.za>
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...

OK, that sounds reasonable. (I missed that in the discussion on the
bug, sorry. I tend not to download files unless I actually am on the
hook for code reviewing them, so any details that were only obvious
from the patch may have gone by me.)

Of course, you should check if those symbols even exist before referencing them.
History
Date User Action Args
2009-02-27 22:27:53gvanrossumsetrecipients: + gvanrossum, exarkun, amaury.forgeotdarc, pitrou, ocean-city, zmedico
2009-02-27 22:27:52gvanrossumlinkissue5380 messages
2009-02-27 22:27:51gvanrossumcreate