bpo-31960: Fix asyncio.Future documentation for thread (un)safety. (#4319)
This commit is contained in:
parent
39a156c505
commit
22b1128559
|
@ -216,7 +216,7 @@ Future
|
|||
raise an exception when the future isn't done yet.
|
||||
|
||||
- Callbacks registered with :meth:`add_done_callback` are always called
|
||||
via the event loop's :meth:`~AbstractEventLoop.call_soon_threadsafe`.
|
||||
via the event loop's :meth:`~AbstractEventLoop.call_soon`.
|
||||
|
||||
- This class is not compatible with the :func:`~concurrent.futures.wait` and
|
||||
:func:`~concurrent.futures.as_completed` functions in the
|
||||
|
|
|
@ -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.
|
||||
|
|
Loading…
Reference in New Issue