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 desbma
Recipients desbma, r.david.murray, serhiy.storchaka
Date 2014-10-23.19:55:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1414094158.21.0.904826534028.issue22712@psf.upfronthosting.co.za>
In-reply-to
Content
I think the 'stdin argument can be any file like or stream for all subprocess functions' approach would be the best solution, because it is misleading to differentiate behavior based on internal implementation details (the use of communicate), when the function names are so close and are expected to have a similar behavior.

It's not that I really need or miss the input argument for check call and call (as you said it is easy to circumvent). 
The issue IMO is that it is unintuitive that it is available for check_output and not others.
History
Date User Action Args
2014-10-23 19:55:58desbmasetrecipients: + desbma, r.david.murray, serhiy.storchaka
2014-10-23 19:55:58desbmasetmessageid: <1414094158.21.0.904826534028.issue22712@psf.upfronthosting.co.za>
2014-10-23 19:55:58desbmalinkissue22712 messages
2014-10-23 19:55:57desbmacreate