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 stutzbach
Recipients benjamin.peterson, doko, petere, pitrou, stutzbach
Date 2009-10-14.00:11:10
SpamBayes Score 1.19782e-05
Marked as misclassified No
Message-id <>
Is it even possible to portably test the validity of a file descriptor
without trying to write/read it?

When I first saw this bug, my gut feeling was "well, don't do that
then!"  However, I then recalled that Windows GUI applications have no
stdin, stdout, or stderr.  

Python 2 will raise IOError: Bad File Descriptor when the user tries to
write to stdout or stderr (more accurately, it raises the exception when
trying to flush data to the file descriptor).  

I just tested pythonw.exe.  If I set sys.stderr by hand to a file, then
write to sys.stdout, 2.6 will correctly write the exception to the file.
 3.1 exits silently.
Date User Action Args
2009-10-14 00:11:14stutzbachsetrecipients: + stutzbach, doko, pitrou, benjamin.peterson, petere
2009-10-14 00:11:13stutzbachsetmessageid: <>
2009-10-14 00:11:12stutzbachlinkissue7111 messages
2009-10-14 00:11:11stutzbachcreate