https://github.com/python/cpython/commit/4f01a120f768d567f6b238f89f13dc349b0... commit: 4f01a120f768d567f6b238f89f13dc349b0a17ed branch: 3.13 author: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com> committer: kumaraditya303 <kumaraditya@python.org> date: 2025-01-09T09:25:18Z summary: [3.13] gh-79149: document reentrant safety of `loop.call_soon_threadsafe` (GH-128662) (#128664) gh-79149: document reentrant safety of `loop.call_soon_threadsafe` (GH-128662) (cherry picked from commit 4685401845ba3e2ab8c9f4a9a10aa2969b11985f) Co-authored-by: Kumar Aditya <kumaraditya@python.org> 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 8d7d0377c132b8..586623b5a78bb3 100644 --- a/Doc/library/asyncio-eventloop.rst +++ b/Doc/library/asyncio-eventloop.rst @@ -236,6 +236,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.