Update docs

python · asvetlov · Jun 30, 2019 · Jun 3, 2019 · Jun 4, 2019 · Jun 4, 2019
commit cc5a7522791045ff9432333b8e98c4d44ff349fb
diff --git a/Doc/library/asyncio-policy.rst b/Doc/library/asyncio-policy.rst
@@ -206,8 +206,7 @@ implementation used by the asyncio event loop:
 
    This implementation starts a new waiting thread for every subprocess spawn.
 
-   The watcher can be used by asyncio code executed in non-main thread without any
-   limitation.
+   It works reliably even when the asyncio event loop is run in a non-main OS thread.
 
    There is no noticeable overhead when handling a big number of children (*O(1)* each
    time a child terminates), but stating a thread per process requires extra memory.
@@ -219,8 +218,8 @@ implementation used by the asyncio event loop:
 .. class:: MultiLoopChildWatcher
 
    This implementation registers a :py:data:`SIGCHLD` signal handler on
-   instantiation. That can break third-party code that installs a custom handler for `SIGCHLD`.
-   signal).
+   instantiation. That can break third-party code that installs a custom handler for
+   `SIGCHLD`.  signal).
 
    The watcher avoids disrupting other code spawning processes
    by polling every process explicitly on a :py:data:`SIGCHLD` signal.

diff --git a/Doc/library/asyncio-subprocess.rst b/Doc/library/asyncio-subprocess.rst
@@ -308,6 +308,9 @@ On UNIX *child watchers* are used for subprocess finish waiting, see
    UNIX switched to use :class:`ThreadedChildWatcher` for spawning subprocesses from
    different threads without any limitation.
 
+   Spawning a subprocess with *inactive* current child watcher raises
+   :exc:`RuntimeError`.
+
 Note that alternative event loop implementations might have own limitations;
 please refer to their documentation.