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.

Title: Adding context in concurrent.futures.ProcessPoolExecutor
Type: enhancement Stage: resolved
Components: Library (Lib) Versions: Python 3.7
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: Nosy List: pitrou, tomMoral
Priority: normal Keywords:

Created on 2017-09-21 09:01 by tomMoral, last changed 2022-04-11 14:58 by admin. This issue is now closed.

Pull Requests
URL Status Linked Edit
PR 3682 merged tomMoral, 2017-09-21 09:01
Messages (2)
msg302674 - (view) Author: Thomas Moreau (tomMoral) * Date: 2017-09-21 09:01
The `ProcessPoolExecutor` processes start method can only be change by changing the global default context with `set_start_method` at the beginning of a script. We propose to allow passing a context argument in the constructor to allow more flexible control of the executor.

Adding this would allow testing `ProcessPoolExecutor` with all the available context
msg303591 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2017-10-03 09:53
New changeset e8c368df22c344183627e7ef882bea1683fe6dbe by Antoine Pitrou (Thomas Moreau) in branch 'master':
bpo-31540: Allow passing multiprocessing context to ProcessPoolExecutor (#3682)
Date User Action Args
2022-04-11 14:58:52adminsetgithub: 75721
2017-10-03 09:58:35pitrousetstatus: open -> closed
resolution: fixed
stage: resolved
2017-10-03 09:53:19pitrousetnosy: + pitrou
messages: + msg303591
2017-09-21 09:01:38tomMoralcreate