gio.subprocess
Module for [Subprocess] class
Types 3
[gio.subprocess.Subprocess] allows the creation of and interaction with child processes.
Processes can be communicated with using standard GIO-style APIs (ie: [gio.input_stream.InputStream], [gio.output_stream.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 [gio.output_stream.OutputStream.spliceAsync]. This makes [gio.subprocess.Subprocess] significantly more powerful and flexible than equivalent APIs in some other languages such as the subprocess.py included with Python. For example, using [gio.subprocess.Subprocess] 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 [gio.subprocess.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.
[gio.subprocess.Subprocess] 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 [gio.subprocess.Subprocess] API (unless [gio.types.SubprocessFlags.InheritFds] was specified).
[gio.subprocess.Subprocess] will quickly reap all child processes as they exit, avoiding ‘zombie processes’ remaining around for long periods of time. [gio.subprocess.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, [gio.subprocess.Subprocess] 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 [gio.types.SubprocessFlags.SearchPathFromEnvp] to use the PATH of the launcher environment instead.
[gio.subprocess.Subprocess] 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 [gio.subprocess.Subprocess.new_]. The [gio.subprocess_launcher.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 [gio.subprocess.Subprocess] will involve calling [gio.subprocess.Subprocess.new_], followed by [gio.subprocess.Subprocess.waitAsync] or [gio.subprocess.Subprocess.wait]. After the process exits, the status can be checked using functions such as [gio.subprocess.Subprocess.getIfExited] (which are similar to the familiar WIFEXITED-style POSIX macros).
Subprocess self()Returns `this`, for use in `with` statements.SubprocessGidBuilder builder()Get builder for [gio.subprocess.Subprocess] Returns: New builder objectgio.subprocess.Subprocess new_(string[] argv, gio.types.SubprocessFlags flags)Create a new process with the given flags and argument list.bool communicate(glib.bytes.Bytes stdinBuf, gio.cancellable.Cancellable cancellable, out glib.bytes.Bytes stdoutBuf, out glib.bytes.Bytes stderrBuf)Communicate with the subprocess until it terminates, and all input and output has been completed.void communicateAsync(glib.bytes.Bytes stdinBuf = null, gio.cancellable.Cancellable cancellable = null, gio.types.AsyncReadyCallback callback = null)Asynchronous version of [gio.subprocess.Subprocess.communicate]. Complete invocation with [gio.subprocess.Subprocess.communicateFinish].bool communicateFinish(gio.async_result.AsyncResult result, out glib.bytes.Bytes stdoutBuf, out glib.bytes.Bytes stderrBuf)Complete an invocation of [gio.subprocess.Subprocess.communicateAsync].bool communicateUtf8(string stdinBuf, gio.cancellable.Cancellable cancellable, out string stdoutBuf, out string stderrBuf)Like [gio.subprocess.Subprocess.communicate], but validates the output of the process as UTF-8, and returns it as a regular NUL terminated string.void communicateUtf8Async(string stdinBuf = null, gio.cancellable.Cancellable cancellable = null, gio.types.AsyncReadyCallback callback = null)Asynchronous version of [gio.subprocess.Subprocess.communicateUtf8]. Complete invocation with [gio.subprocess.Subprocess.communicateUtf8Finish].bool communicateUtf8Finish(gio.async_result.AsyncResult result, out string stdoutBuf, out string stderrBuf)Complete an invocation of [gio.subprocess.Subprocess.communicateUtf8Async].void forceExit()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, ...int getExitStatus()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.string getIdentifier()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 null. Returns: the subproc...bool getIfExited()Check if the given subprocess exited normally (ie: by way of exit() or return from main()).bool getIfSignaled()Check if the given subprocess terminated in response to a signal.int getStatus()Gets the raw status code of the process, as from waitpid().gio.input_stream.InputStream getStderrPipe()Gets the #GInputStream from which to read the stderr output of subprocess.gio.output_stream.OutputStream getStdinPipe()Gets the #GOutputStream that you can write to in order to give data to the stdin of subprocess.gio.input_stream.InputStream getStdoutPipe()Gets the #GInputStream from which to read the stdout output of subprocess.bool getSuccessful()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().int getTermSig()Get the signal number that caused the subprocess to terminate, given that it terminated due to a signal.void sendSignal(int signalNum)Sends the UNIX signal signal_num to the subprocess, if it is still running.bool wait(gio.cancellable.Cancellable cancellable = null)Synchronously wait for the subprocess to terminate.void waitAsync(gio.cancellable.Cancellable cancellable = null, gio.types.AsyncReadyCallback callback = null)Wait for the subprocess to terminate.bool waitCheck(gio.cancellable.Cancellable cancellable = null)Combines [gio.subprocess.Subprocess.wait] with [glib.global.spawnCheckWaitStatus].void waitCheckAsync(gio.cancellable.Cancellable cancellable = null, gio.types.AsyncReadyCallback callback = null)Combines [gio.subprocess.Subprocess.waitAsync] with [glib.global.spawnCheckWaitStatus].bool waitCheckFinish(gio.async_result.AsyncResult result)Collects the result of a previous call to [gio.subprocess.Subprocess.waitCheckAsync].bool waitFinish(gio.async_result.AsyncResult result)Collects the result of a previous call to [gio.subprocess.Subprocess.waitAsync].T flags(gio.types.SubprocessFlags propval)Set `flags` property. Params: propval = Subprocess flags. Returns: Builder instance for fluent chainingFluent builder for [gio.subprocess.Subprocess]