Message 302121 - 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	Leonardo Francalanci, eryksun, martin.panter, r.david.murray
Date	2017-09-13.21:34:15
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1505338455.94.0.579075077241.issue31447@psf.upfronthosting.co.za>
In-reply-to

Content
. Isn’t your use of “cmd” similar enough to shell=True? I.e. isn’t that a “cmd” parent process spawning a “waitfor” child? If your 4 s “subprocess.run” call times out, does it kill the “waitfor” process, or leave it running? Could the “waitfor” process write to stdout or stderr, and should that be captured by your 20 s “communicate” call?

.
Isn’t your use of “cmd” similar enough to shell=True? I.e. isn’t that a “cmd” parent process spawning a “waitfor” child? If your 4 s “subprocess.run” call times out, does it kill the “waitfor” process, or leave it running?

Could the “waitfor” process write to stdout or stderr, and should that be captured by your 20 s “communicate” call?

History
Date	User	Action	Args
2017-09-13 21:34:15	martin.panter	set	recipients: + martin.panter, r.david.murray, eryksun, Leonardo Francalanci
2017-09-13 21:34:15	martin.panter	set	messageid: <1505338455.94.0.579075077241.issue31447@psf.upfronthosting.co.za>
2017-09-13 21:34:15	martin.panter	link	issue31447 messages
2017-09-13 21:34:15	martin.panter	create