8000 gh-79149: document reentrant safety of `loop.call_soon_threadsafe` by kumaraditya303 · Pull Request #128662 · python/cpython · GitHub
[go: up one dir, main page]
Skip to content

gh-79149: document reentrant safety of loop.call_soon_threadsafe #128662

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

Merged
merged 3 commits into from
Jan 9, 2025
Merged

gh-79149: document reentrant safety of loop.call_soon_threadsafe #128662

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
dd061a1
improve docs
kumaraditya303 Jan 9, 2025
4d0006a
Update Doc/library/asyncio-eventloop.rst
kumaraditya303 Jan 9, 2025
1bb1f34
use reentrant
kumaraditya303 Jan 9, 2025
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
Prev Previous commit
Next Next commit
Update Doc/library/asyncio-eventloop.rst 
Co-authored-by: Thomas Grainger <tagrain@gmail.com>
  • Loading branch information
@kumaraditya303 @graingert
kumaraditya303 and graingert authored Jan 9, 2025
commit 4d0006a776bafdcbf81c8e72d2c4896bc34c95ea
3 changes: 2 additions & 1 deletion Doc/library/asyncio-eventloop.rst
8000
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -246,7 +246,8 @@ Scheduling callbacks
another thread, this function *must* be used, since :meth:`call_soon` is not
thread-safe.

This function is safe to be called from a re-entrant context or signal handler.
This function is safe to be called from a re-entrant context or signal handler,
however, it is not safe or fruitful to use the returned handle in such contexts.

Raises :exc:`RuntimeError` if called on a loop that's been closed.
This can happen on a secondary thread when the main application is
Expand Down
Loading
0