https://github.com/python/cpython/commit/04899b8539ab83657a4495203f26b3cb1a6f46dc
commit: 04899b8539ab83657a4495203f26b3cb1a6f46dc
branch: main
author: Gregory P. Smith <[email protected]>
committer: gpshead <[email protected]>
date: 2025-12-30T15:24:32-08:00
summary:
gh-115634: document ProcessPoolExecutor max_tasks_per_child bug (GH-140897)
files:
M Doc/library/concurrent.futures.rst
diff --git a/Doc/library/concurrent.futures.rst
b/Doc/library/concurrent.futures.rst
index c2e2f7f820f4ef..18d92e8e9959a9 100644
--- a/Doc/library/concurrent.futures.rst
+++ b/Doc/library/concurrent.futures.rst
@@ -379,6 +379,11 @@ in a REPL or a lambda should not be expected to work.
default in absence of a *mp_context* parameter. This feature is incompatible
with the "fork" start method.
+ .. note::
+ Bugs have been reported when using the *max_tasks_per_child* feature that
+ can result in the :class:`ProcessPoolExecutor` hanging in some
+ circumstances. Follow its eventual resolution in :gh:`115634`.
+
.. versionchanged:: 3.3
When one of the worker processes terminates abruptly, a
:exc:`~concurrent.futures.process.BrokenProcessPool` error is now raised.
_______________________________________________
Python-checkins mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3//lists/python-checkins.python.org
Member address: [email protected]
