From 4d74a4c9b6f4167c6b9789ba0421106069f9715a Mon Sep 17 00:00:00 2001 From: AN Long Date: Fri, 9 Jan 2026 21:18:32 +0900 Subject: [PATCH] gh-72239: Add note distinguishing concurrent.futures.Future from asyncio.Future (GH-143288) (cherry picked from commit a9ca49d9c699ce4040f1391d9054d88b4098466b) Co-authored-by: AN Long --- Doc/library/concurrent.futures.rst | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/Doc/library/concurrent.futures.rst b/Doc/library/concurrent.futures.rst index 0a2fa48f9a3555..09d7a0d0ec21c3 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