From: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com> Date: Sat, 10 Jan 2026 06:52:18 +0000 (+0100) Subject: [3.13] gh-72239: Add note distinguishing concurrent.futures.Future from asyncio.Futur... X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=d12d7a9c09d94b57a1e9ec51cd64e627e6b865a8;p=thirdparty%2FPython%2Fcpython.git [3.13] gh-72239: Add note distinguishing concurrent.futures.Future from asyncio.Future (GH-143288) (#143608) gh-72239: Add note distinguishing concurrent.futures.Future from asyncio.Future (GH-143288) (cherry picked from commit a9ca49d9c699ce4040f1391d9054d88b4098466b) Co-authored-by: AN Long --- diff --git a/Doc/library/concurrent.futures.rst b/Doc/library/concurrent.futures.rst index 0a2fa48f9a35..09d7a0d0ec21 100644 --- a/Doc/library/concurrent.futures.rst +++ b/Doc/library/concurrent.futures.rst @@ -19,6 +19,11 @@ The asynchronous execution can be performed with threads, using :class:`ProcessPoolExecutor`. Both implement the same interface, which is defined by the abstract :class:`Executor` class. +:class:`concurrent.futures.Future` must not be confused with +:class:`asyncio.Future`, which is designed for use with :mod:`asyncio` +tasks and coroutines. See the :doc:`asyncio's Future ` +documentation for a detailed comparison of the two. + .. include:: ../includes/wasm-notavail.rst Executor Objects