[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 <tematibr@gmail.com>

diff --git a/Doc/library/asyncio-dev.rst b/Doc/library/asyncio-dev.rst
index c7d97008fb490e6d04596e321fd5ad698c5e8e84..a9c3a0183bb72d2be560ee2dff720cf36d022588 100644 (file)
--- 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