From 8ea0fd85bc67438f679491fae29dfe0a3961900a Mon Sep 17 00:00:00 2001 From: "Miss Islington (bot)" <31488909+miss-islington@users.noreply.github.com> Date: Tue, 28 May 2019 20:12:30 -0700 Subject: bpo-26903: Limit ProcessPoolExecutor to 61 workers on Windows (GH-13132) (GH-13643) Co-Authored-By: brianquinlan (cherry picked from commit 39889864c09741909da4ec489459d0197ea8f1fc) Co-authored-by: Brian Quinlan --- Doc/library/concurrent.futures.rst | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'Doc') diff --git a/Doc/library/concurrent.futures.rst b/Doc/library/concurrent.futures.rst index a57491543b..24d684a012 100644 --- a/Doc/library/concurrent.futures.rst +++ b/Doc/library/concurrent.futures.rst @@ -216,6 +216,10 @@ to a :class:`ProcessPoolExecutor` will result in deadlock. given, it will default to the number of processors on the machine. If *max_workers* is lower or equal to ``0``, then a :exc:`ValueError` will be raised. + On Windows, *max_workers* must be equal or lower than ``61``. If it is not + then :exc:`ValueError` will be raised. If *max_workers* is ``None``, then + the default chosen will be at most ``61``, even if more processors are + available. *mp_context* can be a multiprocessing context or None. It will be used to launch the workers. If *mp_context* is ``None`` or not given, the default multiprocessing context is used. -- cgit v1.2.1