Message 346948 - 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	gregory.p.smith
Recipients	gregory.p.smith, haizaar, martin.panter, xtreak
Date	2019-07-01.00:09:59
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<[email protected]>
In-reply-to

Content
Issue 30154 that I've marked as a duplicate demonstrates this problem without using shell=True. The solution I proposed handles that via the additional small timeout on the cleanup side, but still has the caveat that the grandchild processes keep running unless the caller used start_new_session=True. See the PR. We cannot reasonably determine when start_new_session=True should be a default behavior. And I worry that doing it when it should not be will cause unexpected new problems with existing code.

Issue 30154 that I've marked as a duplicate demonstrates this problem without using shell=True.  The solution I proposed handles that via the additional small timeout on the cleanup side, but still has the caveat that the grandchild processes keep running unless the caller used start_new_session=True.

See the PR.

We cannot reasonably determine when start_new_session=True should be a default behavior.  And I worry that doing it when it should not be will cause unexpected new problems with existing code.

History
Date	User	Action	Args
2019-07-01 00:09:59	gregory.p.smith	set	recipients: + gregory.p.smith, martin.panter, xtreak, haizaar
2019-07-01 00:09:59	gregory.p.smith	set	messageid: <[email protected]>
2019-07-01 00:09:59	gregory.p.smith	link	issue37424 messages
2019-07-01 00:09:59	gregory.p.smith	create