From: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com>
Date: Tue, 17 Aug 2021 23:17:29 +0000 (-0700)
Subject: bpo-44508: [Doc] Document failure mode for loop.call_soon_threadsafe (GH-27688)
X-Git-Tag: v3.10.0rc2~86
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=bbb10761b64095425f7f8dcb3bc1f0d8bdee528a;p=thirdparty%2FPython%2Fcpython.git

bpo-44508: [Doc] Document failure mode for loop.call_soon_threadsafe (GH-27688)


Co-authored-by: Łukasz Langa <lukasz@langa.pl>
(cherry picked from commit 3240bc62f4e0afa09964f3afc845697f0a0806b9)

Co-authored-by: meowmeowmeowcat <meowmeowcat1211@gmail.com>
---

diff --git a/Doc/library/asyncio-eventloop.rst b/Doc/library/asyncio-eventloop.rst
index b1609f7bb77f..eee8095bd4c0 100644
--- a/Doc/library/asyncio-eventloop.rst
+++ b/Doc/library/asyncio-eventloop.rst
@@ -216,6 +216,10 @@ Scheduling callbacks
    A thread-safe variant of :meth:`call_soon`.  Must be used to
    schedule callbacks *from another thread*.
 
+   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.
+
    See the :ref:`concurrency and multithreading <asyncio-multithreading>`
    section of the documentation.