Skip to content

PythonQt.QtCore.QProcess · declarations 002

Back to PythonQt.QtCore.QProcess

exitStatus

exitStatus() -> Any

X.exitStatus()

Supplemental documentation: Qt 5 reference:

QProcess::ExitStatus QProcess::exitStatus() const

Returns the exit status of the last process that finished.

On Windows, if the process was terminated with TerminateProcess() from another application, this function will still return NormalExit unless the exit code is less than 0.

This function was introduced in Qt 4.1.

Upstream PySide2 reference signatures (binding differences may apply):

exitStatus(self) -> PySide2.QtCore.QProcess.ExitStatus

Source: https://doc.qt.io/archives/qt-5.15/qprocess.html#exitStatus

finished

finished(*args: Any, **kwargs: Any) -> Any

Native PythonQt.QtCore.QProcess.finished; argument details are not documented.

Supplemental documentation: Qt 5 reference:

[signal] void QProcess::finished(int exitCode, QProcess::ExitStatus exitStatus)

This signal is emitted when the process finishes. exitCode is the exit code of the process (only valid for normal exits), and exitStatus is the exit status. After the process has finished, the buffers in QProcess are still intact. You can still read any data that the process may have written before it finished.

Note: Signal finished is overloaded in this class. To connect to this signal by using the function pointer syntax, Qt provides a convenient helper for obtaining the function pointer as shown in this example:

connect(process, QOverload<int, QProcess::ExitStatus>::of(&QProcess::finished),
    [=](int exitCode, QProcess::ExitStatus exitStatus){ /* ... */ });

See also exitStatus().

Source: https://doc.qt.io/archives/qt-5.15/qprocess.html#finished

inputChannelMode

inputChannelMode() -> Any

X.inputChannelMode()

Supplemental documentation: Qt 5 reference:

QProcess::InputChannelMode QProcess::inputChannelMode() const

Returns the channel mode of the QProcess standard input channel.

This function was introduced in Qt 5.2.

See also setInputChannelMode() and InputChannelMode.

Upstream PySide2 reference signatures (binding differences may apply):

inputChannelMode(self) -> PySide2.QtCore.QProcess.InputChannelMode

Source: https://doc.qt.io/archives/qt-5.15/qprocess.html#inputChannelMode

isSequential

isSequential() -> bool

X.isSequential() -> bool

Supplemental documentation: Qt 5 reference:

[override virtual] bool QProcess::isSequential() const

Reimplements: QIODevice::isSequential() const.

Upstream PySide2 reference signatures (binding differences may apply):

isSequential(self) -> bool

Source: https://doc.qt.io/archives/qt-5.15/qprocess.html#isSequential

kill

kill() -> None

X.kill()

Supplemental documentation: Qt 5 reference:

[slot] void QProcess::kill()

Kills the current process, causing it to exit immediately.

On Windows, kill() uses TerminateProcess, and on Unix and macOS, the SIGKILL signal is sent to the process.

See also terminate().

Upstream PySide2 reference signatures (binding differences may apply):

kill(self) -> None

Source: https://doc.qt.io/archives/qt-5.15/qprocess.html#kill

nullDevice

nullDevice() -> str

X.nullDevice() -> str

Supplemental documentation: Qt 5 reference:

[static] QString QProcess::nullDevice()

The null device of the operating system.

The returned file path uses native directory separators.

This function was introduced in Qt 5.2.

See also QProcess::setStandardInputFile(), QProcess::setStandardOutputFile(), and QProcess::setStandardErrorFile().

Upstream PySide2 reference signatures (binding differences may apply):

nullDevice() -> str

Source: https://doc.qt.io/archives/qt-5.15/qprocess.html#nullDevice

objectNameChanged

objectNameChanged(*args: Any, **kwargs: Any) -> Any

Native PythonQt.QtCore.QProcess.objectNameChanged; argument details are not documented.

open

open(mode: Any) -> bool

X.open(mode) -> bool

Supplemental documentation: Qt 5 reference:

[override virtual] bool QProcess::open(QIODevice::OpenMode mode \= ReadWrite)

Reimplements: QIODevice::open(QIODevice::OpenMode mode).

Starts the program set by setProgram() with arguments set by setArguments(). The OpenMode is set to mode.

This method is an alias for start(), and exists only to fully implement the interface defined by QIODevice.

Returns true if the program has been started.

See also start(), setProgram(), and setArguments().

Upstream PySide2 reference signatures (binding differences may apply):

open(self, mode: PySide2.QtCore.QIODevice.OpenMode=...) -> bool

Source: https://doc.qt.io/archives/qt-5.15/qprocess.html#open

processChannelMode

processChannelMode() -> Any

X.processChannelMode()

Supplemental documentation: Qt 5 reference:

QProcess::ProcessChannelMode QProcess::processChannelMode() const

Returns the channel mode of the QProcess standard output and standard error channels.

This function was introduced in Qt 4.2.

See also setProcessChannelMode(), ProcessChannelMode, and setReadChannel().

Upstream PySide2 reference signatures (binding differences may apply):

processChannelMode(self) -> PySide2.QtCore.QProcess.ProcessChannelMode

Source: https://doc.qt.io/archives/qt-5.15/qprocess.html#processChannelMode

processEnvironment

processEnvironment() -> Any

X.processEnvironment() -> PythonQt.QtCore.QProcessEnvironment

Supplemental documentation: Qt 5 reference:

QProcessEnvironment QProcess::processEnvironment() const

Returns the environment that QProcess will pass to its child process, or an empty object if no environment has been set using setEnvironment() or setProcessEnvironment(). If no environment has been set, the environment of the calling process will be used.

This function was introduced in Qt 4.6.

See also setProcessEnvironment(), setEnvironment(), and QProcessEnvironment::isEmpty().

Upstream PySide2 reference signatures (binding differences may apply):

processEnvironment(self) -> PySide2.QtCore.QProcessEnvironment

Source: https://doc.qt.io/archives/qt-5.15/qprocess.html#processEnvironment

processId

processId() -> int

X.processId() -> int

Supplemental documentation: Qt 5 reference:

qint64 QProcess::processId() const

Returns the native process identifier for the running process, if available. If no process is currently running, 0 is returned.

This function was introduced in Qt 5.3.

Upstream PySide2 reference signatures (binding differences may apply):

processId(self) -> int

Source: https://doc.qt.io/archives/qt-5.15/qprocess.html#processId

program

program() -> str

X.program() -> str

Supplemental documentation: Qt 5 reference:

QString QProcess::program() const

Returns the program the process was last started with.

This function was introduced in Qt 5.0.

See also setProgram() and start().

Upstream PySide2 reference signatures (binding differences may apply):

program(self) -> str

Source: https://doc.qt.io/archives/qt-5.15/qprocess.html#program

readAllStandardError

readAllStandardError() -> Any

X.readAllStandardError() -> PythonQt.QtCore.QByteArray

Supplemental documentation: Qt 5 reference:

QByteArray QProcess::readAllStandardError()

Regardless of the current read channel, this function returns all data available from the standard error of the process as a QByteArray.

See also readyReadStandardError(), readAllStandardOutput(), readChannel(), and setReadChannel().

Upstream PySide2 reference signatures (binding differences may apply):

readAllStandardError(self) -> PySide2.QtCore.QByteArray

Source: https://doc.qt.io/archives/qt-5.15/qprocess.html#readAllStandardError

readAllStandardOutput

readAllStandardOutput() -> Any

X.readAllStandardOutput() -> PythonQt.QtCore.QByteArray

Supplemental documentation: Qt 5 reference:

QByteArray QProcess::readAllStandardOutput()

Regardless of the current read channel, this function returns all data available from the standard output of the process as a QByteArray.

See also readyReadStandardOutput(), readAllStandardError(), readChannel(), and setReadChannel().

Upstream PySide2 reference signatures (binding differences may apply):

readAllStandardOutput(self) -> PySide2.QtCore.QByteArray

Source: https://doc.qt.io/archives/qt-5.15/qprocess.html#readAllStandardOutput

readChannel

readChannel() -> Any

X.readChannel()

Supplemental documentation: Qt 5 reference:

QProcess::ProcessChannel QProcess::readChannel() const

Returns the current read channel of the QProcess.

See also setReadChannel().

Upstream PySide2 reference signatures (binding differences may apply):

readChannel(self) -> PySide2.QtCore.QProcess.ProcessChannel

Source: https://doc.qt.io/archives/qt-5.15/qprocess.html#readChannel

readChannelFinished

readChannelFinished(*args: Any, **kwargs: Any) -> Any

Native PythonQt.QtCore.QProcess.readChannelFinished; argument details are not documented.

readData

readData(data: str, maxlen: int) -> int

X.readData(data, maxlen) -> int

Supplemental documentation: Qt 5 reference:

[override virtual protected] qint64 QProcess::readData(char *data, qint64 maxlen)

Reimplements: QIODevice::readData(char *data, qint64 maxSize).

Upstream PySide2 reference signatures (binding differences may apply):

readData(self, data: str, maxlen: int) -> int

Source: https://doc.qt.io/archives/qt-5.15/qprocess.html#readData

readyRead

readyRead(*args: Any, **kwargs: Any) -> Any

Native PythonQt.QtCore.QProcess.readyRead; argument details are not documented.

readyReadStandardError

readyReadStandardError(*args: Any, **kwargs: Any) -> Any

Native PythonQt.QtCore.QProcess.readyReadStandardError; argument details are not documented.

Supplemental documentation: Qt 5 reference:

[signal] void QProcess::readyReadStandardError()

This signal is emitted when the process has made new data available through its standard error channel (stderr). It is emitted regardless of the current read channel.

Note: This is a private signal. It can be used in signal connections but cannot be emitted by the user.

See also readAllStandardError() and readChannel().

Source: https://doc.qt.io/archives/qt-5.15/qprocess.html#readyReadStandardError

readyReadStandardOutput

readyReadStandardOutput(*args: Any, **kwargs: Any) -> Any

Native PythonQt.QtCore.QProcess.readyReadStandardOutput; argument details are not documented.

Supplemental documentation: Qt 5 reference:

[signal] void QProcess::readyReadStandardOutput()

This signal is emitted when the process has made new data available through its standard output channel (stdout). It is emitted regardless of the current read channel.

Note: This is a private signal. It can be used in signal connections but cannot be emitted by the user.

See also readAllStandardOutput() and readChannel().

Source: https://doc.qt.io/archives/qt-5.15/qprocess.html#readyReadStandardOutput

seek

seek(pos: Any) -> bool

X.seek(pos) -> bool

setArguments

setArguments(arguments: Any) -> None

X.setArguments(arguments)

Supplemental documentation: Qt 5 reference:

void QProcess::setArguments(const QStringList \&arguments)

Set the arguments to pass to the called program when starting the process. This function must be called before start().

This function was introduced in Qt 5.1.

See also start(), setProgram(), and arguments().

Upstream PySide2 reference signatures (binding differences may apply):

setArguments(self, arguments: typing.Sequence[str]) -> None

Source: https://doc.qt.io/archives/qt-5.15/qprocess.html#setArguments

setEnvironment

setEnvironment(environment: Any) -> None

X.setEnvironment(environment)

Upstream PySide2 reference signatures (binding differences may apply):

setEnvironment(self, environment: typing.Sequence[str]) -> None

Source: https://doc.qt.io/archives/qt-5.15/qprocess.html#setEnvironment

setInputChannelMode

setInputChannelMode(mode: Any) -> None

X.setInputChannelMode(mode)

Supplemental documentation: Qt 5 reference:

void QProcess::setInputChannelMode(QProcess::InputChannelMode mode)

Sets the channel mode of the QProcess standard input channel to the mode specified. This mode will be used the next time start() is called.

This function was introduced in Qt 5.2.

See also inputChannelMode() and InputChannelMode.

Upstream PySide2 reference signatures (binding differences may apply):

setInputChannelMode(self, mode: PySide2.QtCore.QProcess.InputChannelMode) -> None

Source: https://doc.qt.io/archives/qt-5.15/qprocess.html#setInputChannelMode

setProcessChannelMode

setProcessChannelMode(mode: Any) -> None

X.setProcessChannelMode(mode)

Supplemental documentation: Qt 5 reference:

void QProcess::setProcessChannelMode(QProcess::ProcessChannelMode mode)

Sets the channel mode of the QProcess standard output and standard error channels to the mode specified. This mode will be used the next time start() is called. For example:

QProcess builder;
builder.setProcessChannelMode(QProcess::MergedChannels);
builder.start("make", QStringList() << "-j2");

if (!builder.waitForFinished())
    qDebug() << "Make failed:" << builder.errorString();
else
    qDebug() << "Make output:" << builder.readAll();

This function was introduced in Qt 4.2.

See also processChannelMode(), ProcessChannelMode, and setReadChannel().

Upstream PySide2 reference signatures (binding differences may apply):

setProcessChannelMode(self, mode: PySide2.QtCore.QProcess.ProcessChannelMode) -> None

Source: https://doc.qt.io/archives/qt-5.15/qprocess.html#setProcessChannelMode

setProcessEnvironment

setProcessEnvironment(environment: Any) -> None

X.setProcessEnvironment(environment)

Supplemental documentation: Qt 5 reference:

void QProcess::setProcessEnvironment(const QProcessEnvironment \&environment)

Sets the environment that QProcess will pass to the child process.

For example, the following code adds the environment variable TMPDIR:

QProcess process;
QProcessEnvironment env = QProcessEnvironment::systemEnvironment();
env.insert("TMPDIR", "C:\\MyApp\\temp"); // Add an environment variable
process.setProcessEnvironment(env);
process.start("myapp");

Note how, on Windows, environment variable names are case-insensitive.

This function was introduced in Qt 4.6.

See also processEnvironment(), QProcessEnvironment::systemEnvironment(), and setEnvironment().

Upstream PySide2 reference signatures (binding differences may apply):

setProcessEnvironment(self, environment: PySide2.QtCore.QProcessEnvironment) -> None

Source: https://doc.qt.io/archives/qt-5.15/qprocess.html#setProcessEnvironment

setProcessState

setProcessState(state: Any) -> None

X.setProcessState(state)

Supplemental documentation: Qt 5 reference:

[protected] void QProcess::setProcessState(QProcess::ProcessState state)

Sets the current state of the QProcess to the state specified.

See also state().

Upstream PySide2 reference signatures (binding differences may apply):

setProcessState(self, state: PySide2.QtCore.QProcess.ProcessState) -> None

Source: https://doc.qt.io/archives/qt-5.15/qprocess.html#setProcessState

setProgram

setProgram(program: str) -> None

X.setProgram(program)

Supplemental documentation: Qt 5 reference:

void QProcess::setProgram(const QString \&program)

Set the program to use when starting the process. This function must be called before start().

This function was introduced in Qt 5.1.

See also start(), setArguments(), and program().

Upstream PySide2 reference signatures (binding differences may apply):

setProgram(self, program: str) -> None

Source: https://doc.qt.io/archives/qt-5.15/qprocess.html#setProgram

setReadChannel

setReadChannel(channel: Any) -> None

X.setReadChannel(channel)

Supplemental documentation: Qt 5 reference:

void QProcess::setReadChannel(QProcess::ProcessChannel channel)

Sets the current read channel of the QProcess to the given channel. The current input channel is used by the functions read(), readAll(), readLine(), and getChar(). It also determines which channel triggers QProcess to emit readyRead().

See also readChannel().

Upstream PySide2 reference signatures (binding differences may apply):

setReadChannel(self, channel: PySide2.QtCore.QProcess.ProcessChannel) -> None

Source: https://doc.qt.io/archives/qt-5.15/qprocess.html#setReadChannel

setStandardErrorFile

setStandardErrorFile(fileName: str, mode: Any) -> None

X.setStandardErrorFile(fileName, mode)

Supplemental documentation: Qt 5 reference:

void QProcess::setStandardErrorFile(const QString \&fileName, QIODevice::OpenMode mode \= Truncate)

Redirects the process' standard error to the file fileName. When the redirection is in place, the standard error read channel is closed: reading from it using read() will always fail, as will readAllStandardError(). The file will be appended to if mode is Append, otherwise, it will be truncated.

See setStandardOutputFile() for more information on how the file is opened.

Note: if setProcessChannelMode() was called with an argument of QProcess::MergedChannels, this function has no effect.

This function was introduced in Qt 4.2.

See also setStandardInputFile(), setStandardOutputFile(), and setStandardOutputProcess().

Upstream PySide2 reference signatures (binding differences may apply):

setStandardErrorFile(self, fileName: str, mode: PySide2.QtCore.QIODevice.OpenMode=...) -> None

Source: https://doc.qt.io/archives/qt-5.15/qprocess.html#setStandardErrorFile

setStandardInputFile

setStandardInputFile(fileName: str) -> None

X.setStandardInputFile(fileName)

Supplemental documentation: Qt 5 reference:

void QProcess::setStandardInputFile(const QString \&fileName)

Redirects the process' standard input to the file indicated by fileName. When an input redirection is in place, the QProcess object will be in read-only mode (calling write() will result in error).

To make the process read EOF right away, pass nullDevice() here. This is cleaner than using closeWriteChannel() before writing any data, because it can be set up prior to starting the process.

If the file fileName does not exist at the moment start() is called or is not readable, starting the process will fail.

Calling setStandardInputFile() after the process has started has no effect.

This function was introduced in Qt 4.2.

See also setStandardOutputFile(), setStandardErrorFile(), and setStandardOutputProcess().

Upstream PySide2 reference signatures (binding differences may apply):

setStandardInputFile(self, fileName: str) -> None

Source: https://doc.qt.io/archives/qt-5.15/qprocess.html#setStandardInputFile

setStandardOutputFile

setStandardOutputFile(fileName: str, mode: Any) -> None

X.setStandardOutputFile(fileName, mode)

Supplemental documentation: Qt 5 reference:

void QProcess::setStandardOutputFile(const QString \&fileName, QIODevice::OpenMode mode \= Truncate)

Redirects the process' standard output to the file fileName. When the redirection is in place, the standard output read channel is closed: reading from it using read() will always fail, as will readAllStandardOutput().

To discard all standard output from the process, pass nullDevice() here. This is more efficient than simply never reading the standard output, as no QProcess buffers are filled.

If the file fileName doesn't exist at the moment start() is called, it will be created. If it cannot be created, the starting will fail.

If the file exists and mode is QIODevice::Truncate, the file will be truncated. Otherwise (if mode is QIODevice::Append), the file will be appended to.

Calling setStandardOutputFile() after the process has started has no effect.

This function was introduced in Qt 4.2.

See also setStandardInputFile(), setStandardErrorFile(), and setStandardOutputProcess().

Upstream PySide2 reference signatures (binding differences may apply):

setStandardOutputFile(self, fileName: str, mode: PySide2.QtCore.QIODevice.OpenMode=...) -> None

Source: https://doc.qt.io/archives/qt-5.15/qprocess.html#setStandardOutputFile

setStandardOutputProcess

setStandardOutputProcess(destination: Any) -> None

X.setStandardOutputProcess(destination)

Supplemental documentation: Qt 5 reference:

void QProcess::setStandardOutputProcess(QProcess *destination)

Pipes the standard output stream of this process to the destination process' standard input.

The following shell command:

command1 | command2

Can be accomplished with QProcess with the following code:

QProcess process1;
QProcess process2;

process1.setStandardOutputProcess(&process2);

process1.start("command1");
process2.start("command2");

This function was introduced in Qt 4.2.

Upstream PySide2 reference signatures (binding differences may apply):

setStandardOutputProcess(self, destination: PySide2.QtCore.QProcess) -> None

Source: https://doc.qt.io/archives/qt-5.15/qprocess.html#setStandardOutputProcess

setWorkingDirectory

setWorkingDirectory(dir: str) -> None

X.setWorkingDirectory(dir)

Supplemental documentation: Qt 5 reference:

void QProcess::setWorkingDirectory(const QString \&dir)

Sets the working directory to dir. QProcess will start the process in this directory. The default behavior is to start the process in the working directory of the calling process.

See also workingDirectory() and start().

Upstream PySide2 reference signatures (binding differences may apply):

setWorkingDirectory(self, dir: str) -> None

Source: https://doc.qt.io/archives/qt-5.15/qprocess.html#setWorkingDirectory

setupChildProcess

setupChildProcess() -> None

X.setupChildProcess()

Supplemental documentation: Qt 5 reference:

[virtual protected] void QProcess::setupChildProcess()

This function is called in the child process context just before the program is executed on Unix or macOS (i.e., after fork(), but before execve()). Reimplement this function to do last minute initialization of the child process. Example:

class SandboxProcess : public QProcess
{
    ...
 protected:
     void setupChildProcess() override;
    ...
};

void SandboxProcess::setupChildProcess()
{
    // Drop all privileges in the child process, and enter
    // a chroot jail.
#if defined Q_OS_UNIX
    ::setgroups(0, 0);
    ::chroot("/etc/safe");
    ::chdir("/");
    ::setgid(safeGid);
    ::setuid(safeUid);
    ::umask(0);
#endif
}

You cannot exit the process (by calling exit(), for instance) from this function. If you need to stop the program before it starts execution, your workaround is to emit finished() and then call exit().

Warning: This function is called by QProcess on Unix and macOS only. On Windows and QNX, it is not called.

Upstream PySide2 reference signatures (binding differences may apply):

setupChildProcess(self) -> None

Source: https://doc.qt.io/archives/qt-5.15/qprocess.html#setupChildProcess

size

size() -> int

X.size() -> int

start

start(program: Any, arguments: Any, mode: Any) -> None

X.start(program, arguments, mode)

Supplemental documentation: Qt 5 reference:

void QProcess::start(const QString \&program, const QStringList \&arguments, QIODevice::OpenMode mode \= ReadWrite)

Starts the given program in a new process, passing the command line arguments in arguments.

The QProcess object will immediately enter the Starting state. If the process starts successfully, QProcess will emit started(); otherwise, errorOccurred() will be emitted.

Note: Processes are started asynchronously, which means the started() and errorOccurred() signals may be delayed. Call waitForStarted() to make sure the process has started (or has failed to start) and those signals have been emitted.

Note: No further splitting of the arguments is performed.

Windows: The arguments are quoted and joined into a command line that is compatible with the CommandLineToArgvW() Windows function. For programs that have different command line quoting requirements, you need to use setNativeArguments(). One notable program that does not follow the CommandLineToArgvW() rules is cmd.exe and, by consequence, all batch scripts.

The OpenMode is set to mode.

If the QProcess object is already running a process, a warning may be printed at the console, and the existing process will continue running unaffected.

See also processId(), started(), waitForStarted(), and setNativeArguments().

void QProcess::start(QIODevice::OpenMode mode \= ReadWrite)

This is an overloaded function.

Starts the program set by setProgram() with arguments set by setArguments(). The OpenMode is set to mode.

This function was introduced in Qt 5.1.

See also open(), setProgram(), and setArguments().

Upstream PySide2 reference signatures (binding differences may apply):

start(self, command: str, mode: PySide2.QtCore.QIODevice.OpenMode=...) -> None
start(self, mode: PySide2.QtCore.QIODevice.OpenMode=...) -> None
start(self, program: str, arguments: typing.Sequence[str], mode: PySide2.QtCore.QIODevice.OpenMode=...) -> None

Source: https://doc.qt.io/archives/qt-5.15/qprocess.html#start

startDetached

startDetached(program: Any, arguments: Any, workingDirectory: Any, pid: Any) -> bool

X.startDetached(program, arguments, workingDirectory, pid) -> bool

Supplemental documentation: Qt 5 reference:

bool QProcess::startDetached(qint64 *pid \= nullptr)

Starts the program set by setProgram() with arguments set by setArguments() in a new process, and detaches from it. Returns true on success; otherwise returns false. If the calling process exits, the detached process will continue to run unaffected.

Unix: The started process will run in its own session and act like a daemon.

The process will be started in the directory set by setWorkingDirectory(). If workingDirectory() is empty, the working directory is inherited from the calling process.

If the function is successful then *pid is set to the process identifier of the started process. Note that the child process may exit and the PID may become invalid without notice. Furthermore, after the child process exits, the same PID may be recycled and used by a completely different process. User code should be careful when using this variable, especially if one intends to forcibly terminate the process by operating system means.

Only the following property setters are supported by startDetached():

All other properties of the QProcess object are ignored.

Note: The called process inherits the console window of the calling process. To suppress console output, redirect standard/error output to QProcess::nullDevice().

This function was introduced in Qt 5.10.

See also start(), startDetached(const QString \&program, const QStringList \&arguments, const QString \&workingDirectory, qint64 *pid), and startDetached(const QString \&command).

[static] bool QProcess::startDetached(const QString \&program, const QStringList \&arguments, const QString \&workingDirectory \= QString(), qint64 *pid \= nullptr)

This function overloads startDetached().

Starts the program program with the arguments arguments in a new process, and detaches from it. Returns true on success; otherwise returns false. If the calling process exits, the detached process will continue to run unaffected.

Argument handling is identical to the respective start() overload.

The process will be started in the directory workingDirectory. If workingDirectory is empty, the working directory is inherited from the calling process.

If the function is successful then *pid is set to the process identifier of the started process.

See also start().

Upstream PySide2 reference signatures (binding differences may apply):

startDetached(command: str) -> bool
startDetached(program: str, arguments: typing.Sequence[str]) -> bool
startDetached(program: str, arguments: typing.Sequence[str], workingDirectory: str) -> typing.Tuple[bool, int]
startDetached(self) -> typing.Tuple[bool, int]

Source: https://doc.qt.io/archives/qt-5.15/qprocess.html#startDetached

started

started(*args: Any, **kwargs: Any) -> Any

Native PythonQt.QtCore.QProcess.started; argument details are not documented.

Supplemental documentation: Qt 5 reference:

[signal] void QProcess::started()

This signal is emitted by QProcess when the process has started, and state() returns Running.

Note: This is a private signal. It can be used in signal connections but cannot be emitted by the user.

Source: https://doc.qt.io/archives/qt-5.15/qprocess.html#started

state

state() -> Any

X.state()

Supplemental documentation: Qt 5 reference:

QProcess::ProcessState QProcess::state() const

Returns the current state of the process.

See also stateChanged() and error().

Upstream PySide2 reference signatures (binding differences may apply):

state(self) -> PySide2.QtCore.QProcess.ProcessState

Source: https://doc.qt.io/archives/qt-5.15/qprocess.html#state