https://github.com/python/cpython/commit/4685401845ba3e2ab8c9f4a9a10aa2969b1... commit: 4685401845ba3e2ab8c9f4a9a10aa2969b11985f branch: main author: Kumar Aditya <kumaraditya@python.org> committer: kumaraditya303 <kumaraditya@python.org> date: 2025-01-09T09:19:05Z summary: gh-79149: document reentrant safety of `loop.call_soon_threadsafe` (#128662) Co-authored-by: Thomas Grainger <tagrain@gmail.com> files: M Doc/library/asyncio-eventloop.rst diff --git a/Doc/library/asyncio-eventloop.rst b/Doc/library/asyncio-eventloop.rst index ccb362d8c31ddf..bfc0d16f023e5e 100644 --- a/Doc/library/asyncio-eventloop.rst +++ b/Doc/library/asyncio-eventloop.rst @@ -246,6 +246,9 @@ 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 reentrant 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 shutting down.