From: Kumar Aditya <kumaraditya@python.org>
Date: Thu, 9 Jan 2025 09:19:05 +0000 (+0530)
Subject: gh-79149: document reentrant safety of `loop.call_soon_threadsafe` (#128662)
X-Git-Tag: v3.14.0a4~62
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=4685401845ba3e2ab8c9f4a9a10aa2969b11985f;p=thirdparty%2FPython%2Fcpython.git

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

Co-authored-by: Thomas Grainger <tagrain@gmail.com>
---

diff --git a/Doc/library/asyncio-eventloop.rst b/Doc/library/asyncio-eventloop.rst
index ccb362d8c31d..bfc0d16f023e 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.