From: Gregory P. Smith <68491+gpshead@users.noreply.github.com>
Date: Tue, 30 Dec 2025 23:24:32 +0000 (-0800)
Subject: gh-115634: document ProcessPoolExecutor max_tasks_per_child bug (GH-140897)
X-Git-Tag: v3.15.0a5~11^2~170
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=04899b8539ab83657a4495203f26b3cb1a6f46dc;p=thirdparty%2FPython%2Fcpython.git

gh-115634: document ProcessPoolExecutor max_tasks_per_child bug (GH-140897)
---

diff --git a/Doc/library/concurrent.futures.rst b/Doc/library/concurrent.futures.rst
index c2e2f7f820f4..18d92e8e9959 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.