:right-sidebar: True SubprocessLauncher =================================================================== .. currentmodule:: gi.repository.Gio .. versionadded:: 2.40 .. class:: SubprocessLauncher(**properties: ~typing.Any) :no-contents-entry: Superclasses: :class:`~gi.repository.GObject.Object` This class contains a set of options for launching child processes, such as where its standard input and output will be directed, the argument list, the environment, and more. While the :obj:`~gi.repository.Gio.Subprocess` class has high level functions covering popular cases, use of this class allows access to more advanced options. It can also be used to launch multiple subprocesses with a similar configuration. Constructors ------------ .. rst-class:: interim-class .. class:: SubprocessLauncher :no-index: .. classmethod:: new(flags: ~gi.repository.Gio.SubprocessFlags) -> ~gi.repository.Gio.SubprocessLauncher Creates a new :obj:`~gi.repository.Gio.SubprocessLauncher`\. The launcher is created with the default options. A copy of the environment of the calling process is made at the time of this call and will be used as the environment that the process is launched in. .. versionadded:: 2.40 :param flags: :obj:`~gi.repository.Gio.SubprocessFlags` Methods ------- .. rst-class:: interim-class .. class:: SubprocessLauncher :no-index: .. method:: close() -> None Closes all the file descriptors previously passed to the object with :func:`~gi.repository.Gio.SubprocessLauncher.take_fd`, :func:`~gi.repository.Gio.SubprocessLauncher.take_stderr_fd`, etc. After calling this method, any subsequent calls to :func:`~gi.repository.Gio.SubprocessLauncher.spawn` or :func:`~gi.repository.Gio.SubprocessLauncher.spawnv` will return :const:`~gi.repository.Gio.IOErrorEnum.CLOSED`. This method is idempotent if called more than once. This function is called automatically when the :obj:`~gi.repository.Gio.SubprocessLauncher` is disposed, but is provided separately so that garbage collected language bindings can call it earlier to guarantee when FDs are closed. .. versionadded:: 2.68 .. method:: getenv(variable: str) -> str | None Returns the value of the environment variable ``variable`` in the environment of processes launched from this launcher. On UNIX, the returned string can be an arbitrary byte string. On Windows, it will be UTF-8. .. versionadded:: 2.40 :param variable: the environment variable to get .. method:: set_cwd(cwd: str) -> None Sets the current working directory that processes will be launched with. By default processes are launched with the current working directory of the launching process at the time of launch. .. versionadded:: 2.40 :param cwd: the cwd for launched processes .. method:: set_environ(env: list[str]) -> None Replace the entire environment of processes launched from this launcher with the given 'environ' variable. Typically you will build this variable by using :func:`~gi.repository.GLib.listenv` to copy the process 'environ' and using the functions :func:`~gi.repository.GLib.environ_setenv`, :func:`~gi.repository.GLib.environ_unsetenv`, etc. As an alternative, you can use :func:`~gi.repository.Gio.SubprocessLauncher.setenv`, :func:`~gi.repository.Gio.SubprocessLauncher.unsetenv`, etc. Pass an empty array to set an empty environment. Pass :const:`None` to inherit the parent process’ environment. As of GLib 2.54, the parent process’ environment will be copied when :func:`~gi.repository.Gio.SubprocessLauncher.set_environ` is called. Previously, it was copied when the subprocess was executed. This means the copied environment may now be modified (using :func:`~gi.repository.Gio.SubprocessLauncher.setenv`, etc.) before launching the subprocess. On UNIX, all strings in this array can be arbitrary byte strings. On Windows, they should be in UTF-8. .. versionadded:: 2.40 :param env: the replacement environment .. method:: set_flags(flags: ~gi.repository.Gio.SubprocessFlags) -> None Sets the flags on the launcher. The default flags are :const:`~gi.repository.Gio.SubprocessFlags.NONE`. You may not set flags that specify conflicting options for how to handle a particular stdio stream (eg: specifying both :const:`~gi.repository.Gio.SubprocessFlags.STDIN_PIPE` and :const:`~gi.repository.Gio.SubprocessFlags.STDIN_INHERIT`). You may also not set a flag that conflicts with a previous call to a function like :func:`~gi.repository.Gio.SubprocessLauncher.set_stdin_file_path` or :func:`~gi.repository.Gio.SubprocessLauncher.take_stdout_fd`. .. versionadded:: 2.40 :param flags: :obj:`~gi.repository.Gio.SubprocessFlags` .. method:: set_stderr_file_path(path: str | None = None) -> None Sets the file path to use as the stderr for spawned processes. If ``path`` is :const:`None` then any previously given path is unset. The file will be created or truncated when the process is spawned, as would be the case if using '2>' at the shell. If you want to send both stdout and stderr to the same file then use :const:`~gi.repository.Gio.SubprocessFlags.STDERR_MERGE`. You may not set a stderr file path if a stderr fd is already set or if the launcher flags contain any flags directing stderr elsewhere. This feature is only available on UNIX. .. versionadded:: 2.40 :param path: a filename or :const:`None` .. method:: set_stdin_file_path(path: str | None = None) -> None Sets the file path to use as the stdin for spawned processes. If ``path`` is :const:`None` then any previously given path is unset. The file must exist or spawning the process will fail. You may not set a stdin file path if a stdin fd is already set or if the launcher flags contain any flags directing stdin elsewhere. This feature is only available on UNIX. .. versionadded:: 2.40 :param path: a filename or :const:`None` .. method:: set_stdout_file_path(path: str | None = None) -> None Sets the file path to use as the stdout for spawned processes. If ``path`` is :const:`None` then any previously given path is unset. The file will be created or truncated when the process is spawned, as would be the case if using '>' at the shell. You may not set a stdout file path if a stdout fd is already set or if the launcher flags contain any flags directing stdout elsewhere. This feature is only available on UNIX. .. versionadded:: 2.40 :param path: a filename or :const:`None` .. method:: setenv(variable: str, value: str, overwrite: bool) -> None Sets the environment variable ``variable`` in the environment of processes launched from this launcher. On UNIX, both the variable's name and value can be arbitrary byte strings, except that the variable's name cannot contain '='. On Windows, they should be in UTF-8. .. versionadded:: 2.40 :param variable: the environment variable to set, must not contain '=' :param value: the new value for the variable :param overwrite: whether to change the variable if it already exists .. method:: spawnv(argv: list[str]) -> ~gi.repository.Gio.Subprocess Creates a :obj:`~gi.repository.Gio.Subprocess` given a provided array of arguments. .. versionadded:: 2.40 :param argv: Command line arguments .. method:: take_fd(source_fd: int, target_fd: int) -> None Transfer an arbitrary file descriptor from parent process to the child. This function takes ownership of the ``source_fd``\; it will be closed in the parent when ``self`` is freed. By default, all file descriptors from the parent will be closed. This function allows you to create (for example) a custom ``pipe()`` or ``socketpair()`` before launching the process, and choose the target descriptor in the child. An example use case is GNUPG, which has a command line argument ``--passphrase-fd`` providing a file descriptor number where it expects the passphrase to be written. :param source_fd: File descriptor in parent process :param target_fd: Target descriptor for child process .. method:: take_stderr_fd(fd: int) -> None Sets the file descriptor to use as the stderr for spawned processes. If ``fd`` is -1 then any previously given fd is unset. Note that the default behaviour is to pass stderr through to the stderr of the parent process. The passed ``fd`` belongs to the :obj:`~gi.repository.Gio.SubprocessLauncher`\. It will be automatically closed when the launcher is finalized. The file descriptor will also be closed on the child side when executing the spawned process. You may not set a stderr fd if a stderr file path is already set or if the launcher flags contain any flags directing stderr elsewhere. This feature is only available on UNIX. .. versionadded:: 2.40 :param fd: a file descriptor, or -1 .. method:: take_stdin_fd(fd: int) -> None Sets the file descriptor to use as the stdin for spawned processes. If ``fd`` is -1 then any previously given fd is unset. Note that if your intention is to have the stdin of the calling process inherited by the child then :const:`~gi.repository.Gio.SubprocessFlags.STDIN_INHERIT` is a better way to go about doing that. The passed ``fd`` is noted but will not be touched in the current process. It is therefore necessary that it be kept open by the caller until the subprocess is spawned. The file descriptor will also not be explicitly closed on the child side, so it must be marked O_CLOEXEC if that's what you want. You may not set a stdin fd if a stdin file path is already set or if the launcher flags contain any flags directing stdin elsewhere. This feature is only available on UNIX. .. versionadded:: 2.40 :param fd: a file descriptor, or -1 .. method:: take_stdout_fd(fd: int) -> None Sets the file descriptor to use as the stdout for spawned processes. If ``fd`` is -1 then any previously given fd is unset. Note that the default behaviour is to pass stdout through to the stdout of the parent process. The passed ``fd`` is noted but will not be touched in the current process. It is therefore necessary that it be kept open by the caller until the subprocess is spawned. The file descriptor will also not be explicitly closed on the child side, so it must be marked O_CLOEXEC if that's what you want. You may not set a stdout fd if a stdout file path is already set or if the launcher flags contain any flags directing stdout elsewhere. This feature is only available on UNIX. .. versionadded:: 2.40 :param fd: a file descriptor, or -1 .. method:: unsetenv(variable: str) -> None Removes the environment variable ``variable`` from the environment of processes launched from this launcher. On UNIX, the variable's name can be an arbitrary byte string not containing '='. On Windows, it should be in UTF-8. .. versionadded:: 2.40 :param variable: the environment variable to unset, must not contain '=' Properties ---------- .. rst-class:: interim-class .. class:: SubprocessLauncher :no-index: .. attribute:: props.flags :type: ~gi.repository.Gio.SubprocessFlags The type of the None singleton. .. versionadded:: 2.40