Skip to content

Warn against creating asyncio synchronization primitives outside loop #153602

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Rufflewind wants to merge 1 commit into
base: 3.14
Choose a base branch
from
+5 −1
Open

Warn against creating asyncio synchronization primitives outside loop #153602

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion Doc/library/asyncio-sync.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ Synchronization Primitives
-----------------------------------------------

asyncio synchronization primitives are designed to be similar to
those of the :mod:`threading` module with two important caveats:
those of the :mod:`threading` module with several important caveats:

* asyncio primitives are not thread-safe, therefore they should not
be used for OS thread synchronization (use :mod:`threading` for
Expand All @@ -21,6 +21,10 @@ those of the :mod:`threading` module with two important caveats:
argument; use the :func:`asyncio.wait_for` function to perform
operations with timeouts.

* asyncio primitives are bound to a specific event loop and must be
constructed inside the loop to function correctly. A common mistake is
constructing them before the loop starts, such as with global variables.

asyncio has the following basic synchronization primitives:

* :class:`Lock`
Expand Down
Loading