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 r.david.murray
Recipients desbma, r.david.murray, serhiy.storchaka
Date 2014-10-23.19:19:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1414091941.4.0.389081283137.issue22712@psf.upfronthosting.co.za>
In-reply-to
Content
call and check_call are designed as APIs that do *not* manage the standard streams of the commands called.  If you want to manage the streams, either use check_output or Popen directly.

Internally, call and check call do *not* use communicate, and it is communicate that supports the input parameter.  The better way to support input for call and check_call would be to implement the full proposal advanced by Serhiy in issue 16624 (and deprecate 'input' entirely).

So, I think this should either be rejected, or turned into an enhancement request for Serhiy's proposal.
History
Date User Action Args
2014-10-23 19:19:01r.david.murraysetrecipients: + r.david.murray, serhiy.storchaka, desbma
2014-10-23 19:19:01r.david.murraysetmessageid: <1414091941.4.0.389081283137.issue22712@psf.upfronthosting.co.za>
2014-10-23 19:19:01r.david.murraylinkissue22712 messages
2014-10-23 19:19:01r.david.murraycreate