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 takluyver
Recipients barry, ethan.furman, gregory.p.smith, martin.panter, r.david.murray, takluyver
Date 2015-02-02.23:19:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1422919153.57.0.791574261029.issue23342@psf.upfronthosting.co.za>
In-reply-to
Content
Third version of the patch (subprocess_run3):

- Simplifies the documentation of the trio (call, check_call, check_output) to describe them in terms of the equivalent run() call.
- Remove a warning about using PIPE with check_output - I believe this was already incorrect, since check_output uses .communicate() internally, it shouldn't have deadlock issues.
- Replace the implementation of check_output() with a call to run().

I didn't reimplement call or check_call - as previously discussed, they are more different from the code in run(), so subtly breaking things is more possible. They are also simpler.
History
Date User Action Args
2015-02-02 23:19:13takluyversetrecipients: + takluyver, barry, gregory.p.smith, r.david.murray, ethan.furman, martin.panter
2015-02-02 23:19:13takluyversetmessageid: <1422919153.57.0.791574261029.issue23342@psf.upfronthosting.co.za>
2015-02-02 23:19:13takluyverlinkissue23342 messages
2015-02-02 23:19:13takluyvercreate