Gio.Subprocess¶
class — extends GObject.Object, Initable
GSubprocess allows the creation of and interaction with child
processes.
Processes can be communicated with using standard GIO-style APIs (ie:
InputStream, OutputStream). There are GIO-style APIs
to wait for process termination (ie: cancellable and with an asynchronous
variant).
There is an API to force a process to terminate, as well as a race-free API for sending UNIX signals to a subprocess.
One major advantage that GIO brings over the core GLib library is
comprehensive API for asynchronous I/O, such
OutputStream.splice_async. This makes GSubprocess
significantly more powerful and flexible than equivalent APIs in
some other languages such as the subprocess.py
included with Python. For example, using GSubprocess one could
create two child processes, reading standard output from the first,
processing it, and writing to the input stream of the second, all
without blocking the main loop.
A powerful Subprocess.communicate API is provided similar to the
communicate() method of subprocess.py. This enables very easy
interaction with a subprocess that has been opened with pipes.
GSubprocess defaults to tight control over the file descriptors open
in the child process, avoiding dangling-FD issues that are caused by
a simple fork()/exec(). The only open file descriptors in the
spawned process are ones that were explicitly specified by the
GSubprocess API (unless G_SUBPROCESS_FLAGS_INHERIT_FDS was
specified).
GSubprocess will quickly reap all child processes as they exit,
avoiding ‘zombie processes’ remaining around for long periods of
time. Subprocess.wait can be used to wait for this to happen,
but it will happen even without the call being explicitly made.
As a matter of principle, GSubprocess has no API that accepts
shell-style space-separated strings. It will, however, match the
typical shell behaviour of searching the PATH for executables that do
not contain a directory separator in their name. By default, the PATH
of the current process is used. You can specify
G_SUBPROCESS_FLAGS_SEARCH_PATH_FROM_ENVP to use the PATH of the
launcher environment instead.
GSubprocess attempts to have a very simple API for most uses (ie:
spawning a subprocess with arguments and support for most typical
kinds of input and output redirection). See Subprocess.new. The
SubprocessLauncher API is provided for more complicated cases
(advanced types of redirection, environment variable manipulation,
change of working directory, child setup functions, etc).
A typical use of GSubprocess will involve calling
Subprocess.new, followed by Subprocess.wait_async or
Subprocess.wait. After the process exits, the status can be
checked using functions such as Subprocess.get_if_exited (which
are similar to the familiar WIFEXITED-style POSIX macros).
Note that as of GLib 2.82, creating a GSubprocess causes the signal
SIGPIPE to be ignored for the remainder of the program. If you are writing
a command-line utility that uses GSubprocess, you may need to take into
account the fact that your program will not automatically be killed
if it tries to write to stdout after it has been closed.
Constructors¶
newv¶
@classmethod
def newv(cls, argv: list[str | bytes | os.PathLike[str] | os.PathLike[bytes]], flags: SubprocessFlags | int) -> Subprocess
Create a new process with the given flags and argument list.
The argument list is expected to be None-terminated.
Parameters:
argv— commandline arguments for the subprocessflags— flags that define the behaviour of the subprocess
Methods¶
communicate¶
def communicate(self, stdin_buf: bytes | None = ..., cancellable: Cancellable | None = ...) -> tuple[bool, bytes, bytes]
Communicate with the subprocess until it terminates, and all input and output has been completed.
If stdin_buf is given, the subprocess must have been created with
SubprocessFlags.STDIN_PIPE. The given data is fed to the
stdin of the subprocess and the pipe is closed (ie: EOF).
At the same time (as not to cause blocking when dealing with large
amounts of data), if SubprocessFlags.STDOUT_PIPE or
SubprocessFlags.STDERR_PIPE were used, reads from those
streams. The data that was read is returned in stdout and/or
the stderr.
If the subprocess was created with SubprocessFlags.STDOUT_PIPE,
stdout_buf will contain the data read from stdout. Otherwise, for
subprocesses not created with SubprocessFlags.STDOUT_PIPE,
stdout_buf will be set to None. Similar provisions apply to
stderr_buf and SubprocessFlags.STDERR_PIPE.
As usual, any output variable may be given as None to ignore it.
If you desire the stdout and stderr data to be interleaved, create
the subprocess with SubprocessFlags.STDOUT_PIPE and
SubprocessFlags.STDERR_MERGE. The merged result will be returned
in stdout_buf and stderr_buf will be set to None.
In case of any error (including cancellation), False will be
returned with error set. Some or all of the stdin data may have
been written. Any stdout or stderr data that has been read will be
discarded. None of the out variables (aside from error) will have
been set to anything in particular and should not be inspected.
In the case that True is returned, the subprocess has exited and the
exit status inspection APIs (eg: Subprocess.get_if_exited,
Subprocess.get_exit_status) may be used.
You should not attempt to use any of the subprocess pipes after starting this function, since they may be left in strange states, even if the operation was cancelled. You should especially not attempt to interact with the pipes while the operation is in progress (either from another thread or if using the asynchronous version).
Parameters:
stdin_buf— data to send to the stdin of the subprocess, orNonecancellable— aCancellable
communicate_async¶
def communicate_async(self, stdin_buf: bytes | None = ..., cancellable: Cancellable | None = ..., callback: Callable[[Subprocess | None, AsyncResult], None] | None = ...) -> None
Asynchronous version of Subprocess.communicate. Complete
invocation with Subprocess.communicate_finish.
Parameters:
stdin_buf— Input data, orNonecancellable— Cancellablecallback— Callback
communicate_finish¶
Complete an invocation of Subprocess.communicate_async.
Parameters:
result— Result
communicate_utf8¶
def communicate_utf8(self, stdin_buf: str | None = ..., cancellable: Cancellable | None = ...) -> tuple[bool, str, str]
Like Subprocess.communicate, but validates the output of the
process as UTF-8, and returns it as a regular NUL terminated string.
On error, stdout_buf and stderr_buf will be set to undefined values and
should not be used.
Parameters:
stdin_buf— data to send to the stdin of the subprocess, orNonecancellable— aCancellable
communicate_utf8_async¶
def communicate_utf8_async(self, stdin_buf: str | None = ..., cancellable: Cancellable | None = ..., callback: Callable[[Subprocess | None, AsyncResult], None] | None = ...) -> None
Asynchronous version of Subprocess.communicate_utf8. Complete
invocation with Subprocess.communicate_utf8_finish.
Parameters:
stdin_buf— Input data, orNonecancellable— Cancellablecallback— Callback
communicate_utf8_finish¶
Complete an invocation of Subprocess.communicate_utf8_async.
Parameters:
result— Result
force_exit¶
Use an operating-system specific method to attempt an immediate,
forceful termination of the process. There is no mechanism to
determine whether or not the request itself was successful;
however, you can use Subprocess.wait to monitor the status of
the process after calling this function.
On Unix, this function sends SIGKILL.
get_exit_status¶
Check the exit status of the subprocess, given that it exited normally. This is the value passed to the exit() system call or the return value from main.
This is equivalent to the system WEXITSTATUS macro.
It is an error to call this function before Subprocess.wait and
unless Subprocess.get_if_exited returned True.
get_identifier¶
On UNIX, returns the process ID as a decimal string.
On Windows, returns the result of GetProcessId() also as a string.
If the subprocess has terminated, this will return None.
get_if_exited¶
Check if the given subprocess exited normally (ie: by way of exit() or return from main()).
This is equivalent to the system WIFEXITED macro.
It is an error to call this function before Subprocess.wait has
returned.
get_if_signaled¶
Check if the given subprocess terminated in response to a signal.
This is equivalent to the system WIFSIGNALED macro.
It is an error to call this function before Subprocess.wait has
returned.
get_status¶
Gets the raw status code of the process, as from waitpid().
This value has no particular meaning, but it can be used with the
macros defined by the system headers such as WIFEXITED. It can also
be used with GLib.spawn_check_wait_status.
It is more likely that you want to use Subprocess.get_if_exited
followed by Subprocess.get_exit_status.
It is an error to call this function before Subprocess.wait has
returned.
get_stderr_pipe¶
Gets the InputStream from which to read the stderr output of
subprocess.
The process must have been created with SubprocessFlags.STDERR_PIPE,
otherwise None will be returned.
get_stdin_pipe¶
Gets the OutputStream that you can write to in order to give data
to the stdin of subprocess.
The process must have been created with SubprocessFlags.STDIN_PIPE and
not SubprocessFlags.STDIN_INHERIT, otherwise None will be returned.
get_stdout_pipe¶
Gets the InputStream from which to read the stdout output of
subprocess.
The process must have been created with SubprocessFlags.STDOUT_PIPE,
otherwise None will be returned.
get_successful¶
Checks if the process was "successful". A process is considered successful if it exited cleanly with an exit status of 0, either by way of the exit() system call or return from main().
It is an error to call this function before Subprocess.wait has
returned.
get_term_sig¶
Get the signal number that caused the subprocess to terminate, given that it terminated due to a signal.
This is equivalent to the system WTERMSIG macro.
It is an error to call this function before Subprocess.wait and
unless Subprocess.get_if_signaled returned True.
send_signal¶
Sends the UNIX signal signal_num to the subprocess, if it is still
running.
This API is race-free. If the subprocess has terminated, it will not be signalled.
This API is not available on Windows.
Parameters:
signal_num— the signal number to send
wait¶
Synchronously wait for the subprocess to terminate.
After the process terminates you can query its exit status with
functions such as Subprocess.get_if_exited and
Subprocess.get_exit_status.
This function does not fail in the case of the subprocess having
abnormal termination. See Subprocess.wait_check for that.
Cancelling cancellable doesn't kill the subprocess. Call
Subprocess.force_exit if it is desirable.
Parameters:
cancellable— aCancellable
wait_async¶
def wait_async(self, cancellable: Cancellable | None = ..., callback: Callable[[Subprocess | None, AsyncResult], None] | None = ...) -> None
Wait for the subprocess to terminate.
This is the asynchronous version of Subprocess.wait.
Parameters:
cancellable— aCancellable, orNonecallback— aGAsyncReadyCallbackto call when the operation is complete
wait_check¶
Combines Subprocess.wait with GLib.spawn_check_wait_status.
Parameters:
cancellable— aCancellable
wait_check_async¶
def wait_check_async(self, cancellable: Cancellable | None = ..., callback: Callable[[Subprocess | None, AsyncResult], None] | None = ...) -> None
Combines Subprocess.wait_async with GLib.spawn_check_wait_status.
This is the asynchronous version of Subprocess.wait_check.
Parameters:
cancellable— aCancellable, orNonecallback— aGAsyncReadyCallbackto call when the operation is complete
wait_check_finish¶
Collects the result of a previous call to
Subprocess.wait_check_async.
Parameters:
result— theAsyncResultpassed to yourGAsyncReadyCallback
wait_finish¶
Collects the result of a previous call to
Subprocess.wait_async.
Parameters:
result— theAsyncResultpassed to yourGAsyncReadyCallback
Properties¶
argv¶
Argument vector.
flags¶
Subprocess flags.