From: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com> Date: Mon, 21 Aug 2023 21:21:26 +0000 (-0700) Subject: [3.11] gh-108224: Fix asyncio doc inconsistency (GH-108230) (#108232) X-Git-Tag: v3.11.5~26 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=4d4871e715737bf699cf9773e275c7993ae13779;p=thirdparty%2FPython%2Fcpython.git [3.11] gh-108224: Fix asyncio doc inconsistency (GH-108230) (#108232) (Spawning subprocesses does not require the event loop to run in the main thread -- only signal handling does.) (cherry picked from commit 1cc391d9e2ea24ca750005335507b52933fc0b52) Co-authored-by: temach --- diff --git a/Doc/library/asyncio-dev.rst b/Doc/library/asyncio-dev.rst index c7d97008fb49..a9c3a0183bb7 100644 --- a/Doc/library/asyncio-dev.rst +++ b/Doc/library/asyncio-dev.rst @@ -99,7 +99,7 @@ To schedule a coroutine object from a different OS thread, the # Wait for the result: result = future.result() -To handle signals and to execute subprocesses, the event loop must be +To handle signals the event loop must be run in the main thread. The :meth:`loop.run_in_executor` method can be used with a