From: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com>
Date: Fri, 15 Aug 2025 14:11:04 +0000 (+0200)
Subject: [3.13] Mention the "context manager" keyword in concurrent.futures documentation... 
X-Git-Tag: v3.13.8~186
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=2c614a8264ecf6aae7c78086fa371cab63a43dca;p=thirdparty%2FPython%2Fcpython.git

[3.13] Mention the "context manager" keyword in concurrent.futures documentation (GH-130976) (#137811)

Mention the "context manager" keyword in concurrent.futures documentation (GH-130976)
(cherry picked from commit 095bc775ecb5d4213767de3feebaa5a98d8c603c)

Co-authored-by: Jakub Stasiak <jakub@stasiak.at>
---

diff --git a/Doc/library/concurrent.futures.rst b/Doc/library/concurrent.futures.rst
index 73134f6a3987..bf98bf23f01c 100644
--- a/Doc/library/concurrent.futures.rst
+++ b/Doc/library/concurrent.futures.rst
@@ -92,10 +92,10 @@ Executor Objects
       executor has started running will be completed prior to this method
       returning. The remaining futures are cancelled.
 
-      You can avoid having to call this method explicitly if you use the
-      :keyword:`with` statement, which will shutdown the :class:`Executor`
-      (waiting as if :meth:`Executor.shutdown` were called with *wait* set to
-      ``True``)::
+      You can avoid having to call this method explicitly if you use the executor
+      as a :term:`context manager` via the  :keyword:`with` statement, which
+      will shutdown the :class:`Executor` (waiting as if :meth:`Executor.shutdown`
+      were called with *wait* set to ``True``)::
 
          import shutil
          with ThreadPoolExecutor(max_workers=4) as e: