Message 329927 - 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	davin
Recipients	barry, davin, kapilt, ned.deily, pitrou, ronaldoussoren
Date	2018-11-14.19:42:27
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1542224547.66.0.788709270274.issue33725@psf.upfronthosting.co.za>
In-reply-to

Content
Given the original post mentioned 2.7.15, I wonder if it is feasible to fork near the beginning of execution, then maintain and pass around a multiprocessing.Pool to be used when needed instead of dynamically forking? Working with legacy code is almost always more interesting than you want it to be.

Given the original post mentioned 2.7.15, I wonder if it is feasible to fork near the beginning of execution, then maintain and pass around a multiprocessing.Pool to be used when needed instead of dynamically forking?  Working with legacy code is almost always more interesting than you want it to be.

History
Date	User	Action	Args
2018-11-14 19:42:27	davin	set	recipients: + davin, barry, ronaldoussoren, pitrou, ned.deily, kapilt
2018-11-14 19:42:27	davin	set	messageid: <1542224547.66.0.788709270274.issue33725@psf.upfronthosting.co.za>
2018-11-14 19:42:27	davin	link	issue33725 messages
2018-11-14 19:42:27	davin	create