From 22b1128559bdeb96907da5840960691bb050d11a Mon Sep 17 00:00:00 2001
From: Antoine Pitrou <pitrou@free.fr>
Date: Tue, 7 Nov 2017 17:03:28 +0100
Subject: bpo-31960: Fix asyncio.Future documentation for thread (un)safety.
 (#4319)

---
 Lib/asyncio/futures.py | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

(limited to 'Lib/asyncio/futures.py')

diff --git a/Lib/asyncio/futures.py b/Lib/asyncio/futures.py
index 215f72d191..3dc9c500b3 100644
--- a/Lib/asyncio/futures.py
+++ b/Lib/asyncio/futures.py
@@ -32,11 +32,13 @@ class Future:
 
     Differences:
 
+    - This class is not thread-safe.
+
     - result() and exception() do not take a timeout argument and
       raise an exception when the future isn't done yet.
 
     - Callbacks registered with add_done_callback() are always called
-      via the event loop's call_soon_threadsafe().
+      via the event loop's call_soon().
 
     - This class is not compatible with the wait() and as_completed()
       methods in the concurrent.futures package.
-- 
cgit v1.2.1