Message93950
| Author |
stutzbach |
| Recipients |
benjamin.peterson, doko, petere, pitrou, stutzbach |
| Date |
2009年10月14日.00:11:10 |
| SpamBayes Score |
1.1978204e-05 |
| Marked as misclassified |
No |
| Message-id |
<1255479073.96.0.2360005122.issue7111@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
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. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2009年10月14日 00:11:14 | stutzbach | set | recipients:
+ stutzbach, doko, pitrou, benjamin.peterson, petere |
| 2009年10月14日 00:11:13 | stutzbach | set | messageid: <1255479073.96.0.2360005122.issue7111@psf.upfronthosting.co.za> |
| 2009年10月14日 00:11:12 | stutzbach | link | issue7111 messages |
| 2009年10月14日 00:11:11 | stutzbach | create |
|