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 gvanrossum, ned.deily
Date 2013-10-21.21:45:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I find it pretty suspicious that when this fails it is always connecting the stdin pipe. That code is also suspect in the AIX failure (issue 19293), although for a different reason.

The only theory I have at this point is that perhaps there's a platform bug on OS X 10.4 and before where the pipe is considered invalid if the process already exits? But the subprocess shouldn't be exiting, so this theory is no good, unless there's also a bug that causes the fork or exec to fail. :-(

Maybe this will go away if we replace the stdin pipe with a socket pair, as we are proposing for issue 19293, without ever understanding why.
Date User Action Args
2013-10-21 21:45:00gvanrossumsetrecipients: + gvanrossum, ned.deily
2013-10-21 21:45:00gvanrossumsetmessageid: <>
2013-10-21 21:45:00gvanrossumlinkissue19294 messages
2013-10-21 21:45:00gvanrossumcreate