Message 411543 - 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	methane
Recipients	gregory.p.smith, methane, yilei
Date	2022-01-25.01:55:56
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1643075756.71.0.808162651115.issue46464@roundup.psfhosted.org>
In-reply-to

Content
> The only way to safely launch worker processes on demand is to spawn a worker launcher process spawned prior to any thread creation that remains idle, with a sole job of spawn new worker processes for us. That sounds complicated. That'd be a feature. Lets go with the bugfix first. fork is not the only way to launch worker process. We have spawn. And sapwn is the default for macOS since Python 3.8. Simple reverting seems not good for macOS users, since they need to pay cost for both of pre-spawning and spawn. Can't we just pre-spawn only when fork is used?

> The only way to safely launch worker processes on demand is to spawn a worker launcher process spawned prior to any thread creation that remains idle, with a sole job of spawn new worker processes for us. That sounds complicated. That'd be a feature. Lets go with the bugfix first.

fork is not the only way to launch worker process. We have spawn. And sapwn is the default for macOS since Python 3.8.

Simple reverting seems not good for macOS users, since they need to pay cost for both of pre-spawning and spawn.
Can't we just pre-spawn only when fork is used?

History
Date	User	Action	Args
2022-01-25 01:55:56	methane	set	recipients: + methane, gregory.p.smith, yilei
2022-01-25 01:55:56	methane	set	messageid: <1643075756.71.0.808162651115.issue46464@roundup.psfhosted.org>
2022-01-25 01:55:56	methane	link	issue46464 messages
2022-01-25 01:55:56	methane	create