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 Olivier.Grisel
Recipients Olivier.Grisel, jnoller, lars, sbt
Date 2013-09-12.12:54:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1378990451.99.0.922599868114.issue18999@psf.upfronthosting.co.za>
In-reply-to
Content
The process pool executor [1] from the concurrent futures API would be suitable to explicitly start and stop the helper process for the `forkserver` mode.

[1] http://docs.python.org/3.4/library/concurrent.futures.html#concurrent.futures.ProcessPoolExecutor

The point would be to have as few state as possible encoded in the multiprocessing module (and its singletons) and move that state information to be directly managed by multiprocessing Process and Pool class instances so that libraries could customize the behavior (start_method, executable, ForkingPIckler reducers registry and so on) without mutating the state of the multiprocessing module singletons.
History
Date User Action Args
2013-09-12 12:54:12Olivier.Griselsetrecipients: + Olivier.Grisel, jnoller, sbt, lars
2013-09-12 12:54:11Olivier.Griselsetmessageid: <1378990451.99.0.922599868114.issue18999@psf.upfronthosting.co.za>
2013-09-12 12:54:11Olivier.Grisellinkissue18999 messages
2013-09-12 12:54:11Olivier.Griselcreate