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 christian.heimes, gvanrossum
Date 2007-11-12.16:58:41
SpamBayes Score 0.48527515
Marked as misclassified No
Message-id <1194886722.08.0.0603927080767.issue1422@psf.upfronthosting.co.za>
In-reply-to
Content
I don't think this is worth fixing; you'll get an I/O error as soon as
I/O is attempted, which is upon the first read() for input, or upon the
firsh (implicit or explicit) flush() on output.  You can't tell whether
a fd is valid or not without attempting I/O on it, so trying to test on
each write() call would defeat the purpose of buffering. Testing on
open() is insufficient as long as anybody could call os.close() any time.
History
Date User Action Args
2007-11-12 16:58:42gvanrossumsetspambayes_score: 0.485275 -> 0.48527515
recipients: + gvanrossum, christian.heimes
2007-11-12 16:58:42gvanrossumsetspambayes_score: 0.485275 -> 0.485275
messageid: <1194886722.08.0.0603927080767.issue1422@psf.upfronthosting.co.za>
2007-11-12 16:58:42gvanrossumlinkissue1422 messages
2007-11-12 16:58:41gvanrossumcreate