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 zwol
Recipients BreamoreBoy, serhiy.storchaka, zwol
Date 2013-04-18.18:39:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Note also that allowing `stdin=<any filelike>` in a clean fashion would require rather more surgery than you suggest, because a filelike can produce an infinite stream of data, and people would expect that to work when the subprocess only reads a finite prefix; making it *actually* work would involve teaching communicate() to take a filelike and copy blocks into the pipe.  I have no *objection* to that change but I think it is too much mission creep for this proposal.

With the present design, where stdin= has to be something for which fileno() is defined, and input= has to be a string (hence of finite length), no one is going to expect something to work that won't.
Date User Action Args
2013-04-18 18:39:34zwolsetrecipients: + zwol, BreamoreBoy, serhiy.storchaka
2013-04-18 18:39:34zwolsetmessageid: <>
2013-04-18 18:39:33zwollinkissue16624 messages
2013-04-18 18:39:33zwolcreate