Message 354293 - 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, vstinner
Date	2019-10-09.18:55:59
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1570647359.67.0.0345389639499.issue38417@roundup.psfhosted.org>
In-reply-to

Content
We should not provide such an "run arbitrary python code before execing the ultimate child" feature in the standard library. It is complicated, and assumes you have an ability to execute a new interpreter with its own slow startup time as an intermediate in the child in the first place. (embedded pythons do not have that ability) Leave that to someone to implement on top of subprocess as a thing on PyPI.

We should not provide such an "run arbitrary python code before execing the ultimate child" feature in the standard library.

It is complicated, and assumes you have an ability to execute a new interpreter with its own slow startup time as an intermediate in the child in the first place.  (embedded pythons do not have that ability)

Leave that to someone to implement on top of subprocess as a thing on PyPI.

History
Date	User	Action	Args
2019-10-09 18:55:59	gregory.p.smith	set	recipients: + gregory.p.smith, vstinner
2019-10-09 18:55:59	gregory.p.smith	set	messageid: <1570647359.67.0.0345389639499.issue38417@roundup.psfhosted.org>
2019-10-09 18:55:59	gregory.p.smith	link	issue38417 messages
2019-10-09 18:55:59	gregory.p.smith	create