Lines Matching +full:in +full:- +full:process

3 .. _asyncio-subprocess:
12 ----------------------------------------
14 This section describes high-level async/await asyncio APIs to
48 and monitor multiple subprocesses in parallel.  It is indeed trivial
70    wrappers for :attr:`Process.stdout` and :attr:`Process.stderr`
73    Return a :class:`~asyncio.subprocess.Process` instance.
88    wrappers for :attr:`Process.stdout` and :attr:`Process.stderr`
91    Return a :class:`~asyncio.subprocess.Process` instance.
102       escape whitespace and special shell characters in strings that are going
111    used. See :ref:`Subprocess Support on Windows <asyncio-windows-subprocess>`
116    asyncio also has the following *low-level* APIs to work with subprocesses:
119    as well as the :ref:`Subprocess Transports <asyncio-subprocess-transports>`
120    and :ref:`Subprocess Protocols <asyncio-subprocess-protocols>`.
132    :attr:`Process.stdin <asyncio.subprocess.Process.stdin>` attribute
136    :attr:`Process.stdout <asyncio.subprocess.Process.stdout>` and
137    :attr:`Process.stderr <asyncio.subprocess.Process.stderr>`
150    to process creation functions.  It indicates that the special file
158 functions return instances of the *Process* class.  *Process* is a high-level
162 .. class:: asyncio.subprocess.Process
173    * unlike Popen, Process instances do not have an equivalent to
176    * the :meth:`~asyncio.subprocess.Process.communicate` and
177      :meth:`~asyncio.subprocess.Process.wait` methods don't have a
180    * the :meth:`Process.wait() <asyncio.subprocess.Process.wait>` method
186    This class is :ref:`not thread safe <asyncio-multithreading>`.
188    See also the :ref:`Subprocess and Threads <asyncio-subprocess-threads>`
193       Wait for the child process to terminate.
200          ``stderr=PIPE`` and the child process generates so much output
207       Interact with process:
211       3. wait for process to terminate.
214       that will be sent to the child process.
220       exception is ignored.  This condition occurs when the process
223       If it is desired to send data to the process' *stdin*,
224       the process needs to be created with ``stdin=PIPE``.  Similarly,
225       to get anything other than ``None`` in the result tuple, the
226       process has to be created with ``stdout=PIPE`` and/or
229       Note, that the data read is buffered in memory, so do not use
234       Sends the signal *signal* to the child process.
245       Stop the child process.
248       child process.
251       called to stop the child process.
255       Kill the child process.
258       process.
265       if the process was created with ``stdin=None``.
270       if the process was created with ``stdout=None``.
275       if the process was created with ``stderr=None``.
280       :attr:`process.stdin.write() <stdin>`,
281       :attr:`await process.stdout.read() <stdout>` or
282       :attr:`await process.stderr.read() <stderr>`.
284       and blocking the child process.
288       Process identification number (PID).
295       Return code of the process when it exits.
297       A ``None`` value indicates that the process has not terminated yet.
299       A negative value ``-N`` indicates that the child was terminated
303 .. _asyncio-subprocess-threads:
306 ----------------------
315 :ref:`asyncio-watchers` for more info.
331    The :ref:`Concurrency and multithreading in asyncio
332    <asyncio-multithreading>` section.
336 --------
338 An example using the :class:`~asyncio.subprocess.Process` class to
356             sys.executable, '-c', code,
372 written using low-level APIs.