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 martin.panter
Recipients Joe.Borg, bbayles, gregory.p.smith, martin.panter, xtreak
Date 2019-05-01.00:01:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1556668901.09.0.986723410403.issue36760@roundup.psfhosted.org>
In-reply-to
Content
Python 3.7 added the "capture_output" parameter, for Issue 32102. Before that change, you could use "subprocess.PIPE":

https://docs.python.org/3.6/library/subprocess.html#subprocess.run
“To [capture output], pass PIPE for the ‘stdout’ and/or ‘stderr’ arguments”

Since "capture_output" was added, it looks like you can still pass "subprocess.PIPE" on your own, but the documentation now only gives subtle hints that this might be supported. This was also brought up in Issue 33319.
History
Date User Action Args
2019-05-01 00:01:41martin.pantersetrecipients: + martin.panter, gregory.p.smith, Joe.Borg, bbayles, xtreak
2019-05-01 00:01:41martin.pantersetmessageid: <1556668901.09.0.986723410403.issue36760@roundup.psfhosted.org>
2019-05-01 00:01:41martin.panterlinkissue36760 messages
2019-05-01 00:01:40martin.pantercreate