Message 243634 - Python tracker

➜

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	OG7, akira, martin.panter
Date	2015-05-19.22:52:38
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1432075959.16.0.57122673624.issue6445@psf.upfronthosting.co.za>
In-reply-to

Content
In the mean time, a subprocess.run() API has been added which can call communicate() and raise CalledProcessError in one step (depending on arguments). See Issue 23342. This might satisfy some use cases, but maybe adding the check functionality to the low-level API would be nice as well. Perhaps a separate check_exit_status() method would be more flexible? Or maybe a flag stored in the subprocess object that causes wait() and poll() to do the check?

In the mean time, a subprocess.run() API has been added which can call communicate() and raise CalledProcessError in one step (depending on arguments). See Issue 23342. This might satisfy some use cases, but maybe adding the check functionality to the low-level API would be nice as well.

Perhaps a separate check_exit_status() method would be more flexible? Or maybe a flag stored in the subprocess object that causes wait() and poll() to do the check?

History
Date	User	Action	Args
2015-05-19 22:52:39	martin.panter	set	recipients: + martin.panter, OG7, akira
2015-05-19 22:52:39	martin.panter	set	messageid: <1432075959.16.0.57122673624.issue6445@psf.upfronthosting.co.za>
2015-05-19 22:52:39	martin.panter	link	issue6445 messages
2015-05-19 22:52:38	martin.panter	create