python-docs-fa/library/asyncio-subprocess.po at 3.14 · python/python-docs-fa

314 lines (234 loc) · 11.9 KB
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2001 Python Software Foundation
# This file is distributed under the same license as the Python package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
# Translators:
# Danial Behzadi <dani.behzi@ubuntu.com>, 2025
# Parham Forati, 2025
# Rafael Fontenelle <rffontenelle@gmail.com>, 2025
# Revisto <theRevisto@gmail.com>, 2025
# Sepehr Rasouli <sepehrrasouli06@gmail.com>, 2026
"Project-Id-Version: Python 3.14\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2026-08-18 04:30+0000\n"
"PO-Revision-Date: 2021-06-28 00:55+0000\n"
"Last-Translator: Sepehr Rasouli <sepehrrasouli06@gmail.com>, 2026\n"
"Language-Team: Persian (https://github.com/revisto/python-docs-fa/fa/)\n"
"Language: fa\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
msgid "Subprocesses"
msgid "**Source code:** :source:`Lib/asyncio/subprocess.py`, :source:`Lib/asyncio/base_subprocess.py`"
msgid "This section describes high-level async/await asyncio APIs to create and manage subprocesses."
msgid "Here's an example of how asyncio can run a shell command and obtain its result::"
"import asyncio\n"
"async def run(cmd):\n"
"    proc = await asyncio.create_subprocess_shell(\n"
"        cmd,\n"
"        stdout=asyncio.subprocess.PIPE,\n"
"        stderr=asyncio.subprocess.PIPE)\n"
"    stdout, stderr = await proc.communicate()\n"
"    print(f'[{cmd!r} exited with {proc.returncode}]')\n"
"    if stdout:\n"
"        print(f'[stdout]\\n{stdout.decode()}')\n"
"    if stderr:\n"
"        print(f'[stderr]\\n{stderr.decode()}')\n"
"asyncio.run(run('ls /zzz'))"
msgid "will print::"
"['ls /zzz' exited with 1]\n"
"[stderr]\n"
"ls: /zzz: No such file or directory"
msgid "Because all asyncio subprocess functions are asynchronous and asyncio provides many tools to work with such functions, it is easy to execute and monitor multiple subprocesses in parallel.  It is indeed trivial to modify the above example to run several commands simultaneously::"
"async def main():\n"
"    await asyncio.gather(\n"
"        run('ls /zzz'),\n"
"        run('sleep 1; echo \"hello\"'))\n"
"asyncio.run(main())"
msgid "See also the `Examples`_ subsection."
msgid "Creating Subprocesses"
msgid "Create a subprocess."
msgid "The *limit* argument sets the buffer limit for :class:`StreamReader` wrappers for :attr:`~asyncio.subprocess.Process.stdout` and :attr:`~asyncio.subprocess.Process.stderr` (if :const:`subprocess.PIPE` is passed to *stdout* and *stderr* arguments)."
msgid "Return a :class:`~asyncio.subprocess.Process` instance."
msgid "See the documentation of :meth:`loop.subprocess_exec` for other parameters."
msgid "If the process object is garbage collected while the process is still running, the child process will be killed."
msgid "Removed the *loop* parameter."
msgid "Run the *cmd* shell command."
msgid "See the documentation of :meth:`loop.subprocess_shell` for other parameters."
msgid "It is the application's responsibility to ensure that all whitespace and special characters are quoted appropriately to avoid `shell injection <https://en.wikipedia.org/wiki/Shell_injection#Shell_injection>`_ vulnerabilities. The :func:`shlex.quote` function can be used to properly escape whitespace and special shell characters in strings that are going to be used to construct shell commands."
msgid "Subprocesses are available for Windows if a :class:`ProactorEventLoop` is used. See :ref:`Subprocess Support on Windows <asyncio-windows-subprocess>` for details."
msgid "asyncio also has the following *low-level* APIs to work with subprocesses: :meth:`loop.subprocess_exec`, :meth:`loop.subprocess_shell`, :meth:`loop.connect_read_pipe`, :meth:`loop.connect_write_pipe`, as well as the :ref:`Subprocess Transports <asyncio-subprocess-transports>` and :ref:`Subprocess Protocols <asyncio-subprocess-protocols>`."
msgid "Constants"
msgid "Can be passed to the *stdin*, *stdout* or *stderr* parameters."
msgid "If *PIPE* is passed to *stdin* argument, the :attr:`Process.stdin <asyncio.subprocess.Process.stdin>` attribute will point to a :class:`~asyncio.StreamWriter` instance."
msgid "If *PIPE* is passed to *stdout* or *stderr* arguments, the :attr:`Process.stdout <asyncio.subprocess.Process.stdout>` and :attr:`Process.stderr <asyncio.subprocess.Process.stderr>` attributes will point to :class:`~asyncio.StreamReader` instances."
msgid "Special value that can be used as the *stderr* argument and indicates that standard error should be redirected into standard output."
msgid "Special value that can be used as the *stdin*, *stdout* or *stderr* argument to process creation functions.  It indicates that the special file :data:`os.devnull` will be used for the corresponding subprocess stream."
msgid "Interacting with Subprocesses"
msgid "Both :func:`create_subprocess_exec` and :func:`create_subprocess_shell` functions return instances of the *Process* class.  *Process* is a high-level wrapper that allows communicating with subprocesses and watching for their completion."
msgid "An object that wraps OS processes created by the :func:`~asyncio.create_subprocess_exec` and :func:`~asyncio.create_subprocess_shell` functions."
msgid "This class is designed to have a similar API to the :class:`subprocess.Popen` class, but there are some notable differences:"
msgid "unlike Popen, Process instances do not have an equivalent to the :meth:`~subprocess.Popen.poll` method;"
msgid "the :meth:`~asyncio.subprocess.Process.communicate` and :meth:`~asyncio.subprocess.Process.wait` methods don't have a *timeout* parameter: use the :func:`~asyncio.wait_for` function;"
msgid "the :meth:`Process.wait() <asyncio.subprocess.Process.wait>` method is asynchronous, whereas :meth:`subprocess.Popen.wait` method is implemented as a blocking busy loop;"
msgid "the *universal_newlines* parameter is not supported."
msgid "This class is :ref:`not thread safe <asyncio-multithreading>`."
msgid "See also the :ref:`Subprocess and Threads <asyncio-subprocess-threads>` section."
msgid "Wait for the child process to terminate."
msgid "Set and return the :attr:`returncode` attribute."
msgid "This method can deadlock when using ``stdout=PIPE`` or ``stderr=PIPE`` and the child process generates so much output that it blocks waiting for the OS pipe buffer to accept more data. Use the :meth:`communicate` method when using pipes to avoid this condition."
msgid "Interact with process:"
msgid "send data to *stdin* (if *input* is not ``None``);"
msgid "closes *stdin*;"
msgid "read data from *stdout* and *stderr*, until EOF is reached;"
msgid "wait for process to terminate."
msgid "The optional *input* argument is the data (:class:`bytes` object) that will be sent to the child process."
msgid "Return a tuple ``(stdout_data, stderr_data)``."
msgid "If either :exc:`BrokenPipeError` or :exc:`ConnectionResetError` exception is raised when writing *input* into *stdin*, the exception is ignored.  This condition occurs when the process exits before all data are written into *stdin*."
msgid "If it is desired to send data to the process' *stdin*, the process needs to be created with ``stdin=PIPE``.  Similarly, to get anything other than ``None`` in the result tuple, the process has to be created with ``stdout=PIPE`` and/or ``stderr=PIPE`` arguments."
msgid "Note, that the data read is buffered in memory, so do not use this method if the data size is large or unlimited."
msgid "*stdin* gets closed when ``input=None`` too."
msgid "Sends the signal *signal* to the child process."
msgid "On Windows, :py:const:`~signal.SIGTERM` is an alias for :meth:`terminate`. ``CTRL_C_EVENT`` and ``CTRL_BREAK_EVENT`` can be sent to processes started with a *creationflags* parameter which includes ``CREATE_NEW_PROCESS_GROUP``."
msgid "Stop the child process."
msgid "On POSIX systems this method sends :py:const:`~signal.SIGTERM` to the child process."
msgid "On Windows the Win32 API function :c:func:`!TerminateProcess` is called to stop the child process."
msgid "Kill the child process."
msgid "On POSIX systems this method sends :py:data:`~signal.SIGKILL` to the child process."
msgid "On Windows this method is an alias for :meth:`terminate`."
msgid "Standard input stream (:class:`~asyncio.StreamWriter`) or ``None`` if the process was created with ``stdin=None``."
msgid "Standard output stream (:class:`~asyncio.StreamReader`) or ``None`` if the process was created with ``stdout=None``."
msgid "Standard error stream (:class:`~asyncio.StreamReader`) or ``None`` if the process was created with ``stderr=None``."
msgid "Use the :meth:`communicate` method rather than :attr:`process.stdin.write() <stdin>`, :attr:`await process.stdout.read() <stdout>` or :attr:`await process.stderr.read() <stderr>`. This avoids deadlocks due to streams pausing reading or writing and blocking the child process."
msgid "Process identification number (PID)."
msgid "Note that for processes created by the :func:`~asyncio.create_subprocess_shell` function, this attribute is the PID of the spawned shell."
msgid "Return code of the process when it exits."
msgid "A ``None`` value indicates that the process has not terminated yet."
msgid "For processes created with :func:`~asyncio.create_subprocess_exec`, a negative value ``-N`` indicates that the child was terminated by signal ``N`` (POSIX only)."
msgid "For processes created with :func:`~asyncio.create_subprocess_shell`, the return code reflects the exit status of the shell itself (e.g. ``/bin/sh``), which may map signals to codes such as ``128+N``. See the documentation of the shell (for example, the Bash manual's Exit Status) for details."
msgid "Subprocess and Threads"
msgid "Standard asyncio event loop supports running subprocesses from different threads by default."
msgid "On Windows subprocesses are provided by :class:`ProactorEventLoop` only (default), :class:`SelectorEventLoop` has no subprocess support."
msgid "Note that alternative event loop implementations might have own limitations; please refer to their documentation."
msgid "The :ref:`Concurrency and multithreading in asyncio <asyncio-multithreading>` section."
msgid "Examples"
msgid "An example using the :class:`~asyncio.subprocess.Process` class to control a subprocess and the :class:`StreamReader` class to read from its standard output."
msgid "The subprocess is created by the :func:`create_subprocess_exec` function::"
"import asyncio\n"
"import sys\n"
"async def get_date():\n"
"    code = 'import datetime as dt; print(dt.datetime.now())'\n"
"    # Create the subprocess; redirect the standard output\n"
"    # into a pipe.\n"
"    proc = await asyncio.create_subprocess_exec(\n"
"        sys.executable, '-c', code,\n"
"        stdout=asyncio.subprocess.PIPE)\n"
"    # Read one line of output.\n"
"    data = await proc.stdout.readline()\n"
"    line = data.decode('ascii').rstrip()\n"
"    # Wait for the subprocess exit.\n"
"    await proc.wait()\n"
"    return line\n"
"date = asyncio.run(get_date())\n"
"print(f\"Current date: {date}\")"
msgid "See also the :ref:`same example <asyncio_example_subprocess_proto>` written using low-level APIs."
Navigation Menu

Uh oh!

Uh oh!

FilesExpand file tree

asyncio-subprocess.po

Latest commit

History

asyncio-subprocess.po

File metadata and controls
