From: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com> Date: Thu, 9 Jan 2025 09:26:40 +0000 (+0100) Subject: [3.12] gh-79149: document reentrant safety of `loop.call_soon_threadsafe` (GH-128662... X-Git-Tag: v3.12.9~91 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=a784cdf6e72788ecb6b671d09b6c5e9c54b0b13e;p=thirdparty%2FPython%2Fcpython.git [3.12] gh-79149: document reentrant safety of `loop.call_soon_threadsafe` (GH-128662) (#128665) gh-79149: document reentrant safety of `loop.call_soon_threadsafe` (GH-128662) (cherry picked from commit 4685401845ba3e2ab8c9f4a9a10aa2969b11985f) Co-authored-by: Kumar Aditya Co-authored-by: Thomas Grainger --- diff --git a/Doc/library/asyncio-eventloop.rst b/Doc/library/asyncio-eventloop.rst index 53aaae413027..8d26346c6301 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.