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 rtpg
Recipients josh.r, martin.panter, rtpg, terry.reedy, xiang.zhang
Date 2017-04-10.01:31:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1491787890.61.0.875711278756.issue29989@psf.upfronthosting.co.za>
In-reply-to
Content
I'm sorry for the confusion here, it turns out I was misinterpreting the results of my program and my workaround was not working. Like others have said, the subprocess code seems to rely on the existence of file descriptors

I would be pretty partial to the idea of having the subprocess's internal code catch OSError and raise a clearer error message like "subprocess can only operate on files with file descriptor support".

Having "complete" file object support would seem like a major win, but looking at the internals/OS support it seems like a hard thing to set up.
History
Date User Action Args
2017-04-10 01:31:30rtpgsetrecipients: + rtpg, terry.reedy, martin.panter, josh.r, xiang.zhang
2017-04-10 01:31:30rtpgsetmessageid: <1491787890.61.0.875711278756.issue29989@psf.upfronthosting.co.za>
2017-04-10 01:31:30rtpglinkissue29989 messages
2017-04-10 01:31:30rtpgcreate