Antoine Pitrou <pit...@free.fr> added the comment:
Well, it occurred today again :)
http://www.python.org/dev/buildbot/all/builders/x86%20Tiger%203.x/builds/1884/steps/test/logs/stdio
test test_cmd_line failed -- Traceback (most recent call last):
File "/Users/db3l/buildarea/3.x.bolen-tiger/build/Lib/test/test_cmd_line.py",
line 95, in test_run_code
assert_python_failure('-c')
File "/Users/db3l/buildarea/3.x.bolen-tiger/build/Lib/test/script_helper.py",
line 57, in assert_python_failure
return _assert_python(False, *args, **env_vars)
File "/Users/db3l/buildarea/3.x.bolen-tiger/build/Lib/test/script_helper.py",
line 30, in _assert_python
env=env)
File "/Users/db3l/buildarea/3.x.bolen-tiger/build/Lib/subprocess.py", line
721, in __init__
self.stdin = io.open(p2cwrite, 'wb', bufsize)
OSError: [Errno 9] Bad file descriptor
But I would suggest an OS X bug instead. My random guess is that the child
process exits very quickly (as you see, it runs "python -c" which is an
immediate error), therefore the other end of the pipe gets closed and OS X then
returns EBADF when we try to do something with our end of the pipe.
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue8458>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
