From 9e79a564773651c874442bd915e05bf6a0a3336e Mon Sep 17 00:00:00 2001 From: Roger Iyengar Date: Mon, 15 Jun 2020 01:06:45 -0400 Subject: [PATCH 1/3] Update asyncio-dev.rst --- Doc/library/asyncio-dev.rst | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/Doc/library/asyncio-dev.rst b/Doc/library/asyncio-dev.rst index ff51c4fa3b20f4..6bc4026db0079f 100644 --- a/Doc/library/asyncio-dev.rst +++ b/Doc/library/asyncio-dev.rst @@ -107,6 +107,16 @@ The :meth:`loop.run_in_executor` method can be used with a blocking code in a different OS thread without blocking the OS thread that the event loop runs in. +There is no way to schedule coroutines or callbacks directly from a +different process (such as one started with :mod:`multiprocessing`). +The :ref:`Event Loop Methods ` section lists APIs +that can read from pipes and watch file descriptors without blocking +the event loop. In addition, asyncio's +:ref:`Subprocess ` APIs provide a way to start a +process and communicate with it from the event loop. Lastly, the +aforementioned :meth:`loop.run_in_executor` method can also be used +with a :class:`concurrent.futures.ProcessPoolExecutor` to execute +code in a different process. .. _asyncio-handle-blocking: From 1a767d0878952396ca2c318de45a574debbe672a Mon Sep 17 00:00:00 2001 From: Roger Iyengar Date: Mon, 15 Jun 2020 01:41:00 -0400 Subject: [PATCH 2/3] Update asyncio-dev.rst --- Doc/library/asyncio-dev.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/Doc/library/asyncio-dev.rst b/Doc/library/asyncio-dev.rst index 6bc4026db0079f..1588580b2cb3d1 100644 --- a/Doc/library/asyncio-dev.rst +++ b/Doc/library/asyncio-dev.rst @@ -107,15 +107,15 @@ The :meth:`loop.run_in_executor` method can be used with a blocking code in a different OS thread without blocking the OS thread that the event loop runs in. -There is no way to schedule coroutines or callbacks directly from a +There is no way to schedule coroutines or callbacks directly from a different process (such as one started with :mod:`multiprocessing`). The :ref:`Event Loop Methods ` section lists APIs -that can read from pipes and watch file descriptors without blocking -the event loop. In addition, asyncio's +that can read from pipes and watch file descriptors without blocking +the event loop. In addition, asyncio's :ref:`Subprocess ` APIs provide a way to start a process and communicate with it from the event loop. Lastly, the aforementioned :meth:`loop.run_in_executor` method can also be used -with a :class:`concurrent.futures.ProcessPoolExecutor` to execute +with a :class:`concurrent.futures.ProcessPoolExecutor` to execute code in a different process. .. _asyncio-handle-blocking: From 12ef443f29a64412d439fed945a073455bfd4e15 Mon Sep 17 00:00:00 2001 From: Roger Iyengar Date: Tue, 21 Jul 2020 01:47:46 -0400 Subject: [PATCH 3/3] Update asyncio-dev.rst --- Doc/library/asyncio-dev.rst | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/Doc/library/asyncio-dev.rst b/Doc/library/asyncio-dev.rst index 1588580b2cb3d1..7234c094498248 100644 --- a/Doc/library/asyncio-dev.rst +++ b/Doc/library/asyncio-dev.rst @@ -107,11 +107,11 @@ The :meth:`loop.run_in_executor` method can be used with a blocking code in a different OS thread without blocking the OS thread that the event loop runs in. -There is no way to schedule coroutines or callbacks directly from a -different process (such as one started with :mod:`multiprocessing`). -The :ref:`Event Loop Methods ` section lists APIs -that can read from pipes and watch file descriptors without blocking -the event loop. In addition, asyncio's +There is currently no way to schedule coroutines or callbacks directly +from a different process (such as one started with +:mod:`multiprocessing`). The :ref:`Event Loop Methods ` +section lists APIs that can read from pipes and watch file descriptors +without blocking the event loop. In addition, asyncio's :ref:`Subprocess ` APIs provide a way to start a process and communicate with it from the event loop. Lastly, the aforementioned :meth:`loop.run_in_executor` method can also be used