QSysInfo#

The QSysInfo class provides information about the system. More…

Synopsis#

Static functions#

def bootUniqueId ()
def buildAbi ()
def buildCpuArchitecture ()
def currentCpuArchitecture ()
def kernelType ()
def kernelVersion ()
def machineHostName ()
def machineUniqueId ()
def prettyProductName ()
def productType ()
def productVersion ()

Note

This documentation may contain snippets that were automatically translated from C++ to Python. We always welcome contributions to the snippet translation. If you see an issue with the translation, you can also let us know by creating a ticket on https:/bugreports.qt.io/projects/PYSIDE

Detailed Description#

WordSize specifies the size of a pointer for the platform on which the application is compiled.

ByteOrder specifies whether the platform is big-endian or little-endian.

Some constants are defined only on certain platforms. You can use the preprocessor symbols Q_OS_WIN and Q_OS_MACOS to test that the application is compiled under Windows or macOS.

See also

QLibraryInfo

class PySide6.QtCore.QSysInfo#

PySide6.QtCore.QSysInfo.Sizes#

This enum provides platform-specific information about the sizes of data structures used by the underlying architecture.

Constant

Description

QSysInfo.WordSize

The size in bits of a pointer for the platform on which the application is compiled (32 or 64).

Constant	Description
QSysInfo.WordSize	The size in bits of a pointer for the platform on which the application is compiled (32 or 64).

PySide6.QtCore.QSysInfo.Endian#

Constant	Description
QSysInfo.BigEndian	Big-endian byte order (also called Network byte order)
QSysInfo.LittleEndian	Little-endian byte order
QSysInfo.ByteOrder	Equals BigEndian or LittleEndian, depending on the platform’s byte order.

static PySide6.QtCore.QSysInfo.bootUniqueId()#

Return type:: PySide6.QtCore.QByteArray

Returns a unique ID for this machine’s boot, if one can be determined. If no unique ID could be determined, this function returns an empty byte array. This value is expected to change after every boot and can be considered globally unique.

This function is currently only implemented for Linux and Apple operating systems.

See also

machineUniqueId()

static PySide6.QtCore.QSysInfo.buildAbi()#

Return type:: str

Returns the full architecture string that Qt was compiled for. This string is useful for identifying different, incompatible builds. For example, it can be used as an identifier to request an upgrade package from a server.

The values returned from this function are kept stable as follows: the mandatory components of the result will not change in future versions of Qt, but optional suffixes may be added.

The returned value is composed of three or more parts, separated by dashes (“-“). They are:

Component

Value

CPU Architecture

The same as buildCpuArchitecture() , such as “arm”, “i386”, “mips” or “x86_64”

Endianness

“ little_endian “ or “ big_endian “

Word size

Whether it’s a 32- or 64-bit application. Possible values are: “llp64” (Windows 64-bit), “lp64” (Unix 64-bit), “ilp32” (32-bit)

(Optional) ABI

Zero or more components identifying different ABIs possible in this architecture. Currently, Qt has optional ABI components for ARM and MIPS processors: one component is the main ABI (such as “eabi”, “o32”, “n32”, “o64”); another is whether the calling convention is using hardware floating point registers (“hardfloat” is present).

Additionally, if Qt was configured with -qreal float, the ABI option tag “qreal_float” will be present. If Qt was configured with another type as qreal, that type is present after “qreal_”, with all characters other than letters and digits escaped by an underscore, followed by two hex digits. For example, -qreal long double becomes “qreal_long_20double”.

See also

buildCpuArchitecture()

Component	Value
CPU Architecture	The same as `buildCpuArchitecture()` , such as “arm”, “i386”, “mips” or “x86_64”
Endianness	“ `little_endian` “ or “ `big_endian` “
Word size	Whether it’s a 32- or 64-bit application. Possible values are: “llp64” (Windows 64-bit), “lp64” (Unix 64-bit), “ilp32” (32-bit)
(Optional) ABI	Zero or more components identifying different ABIs possible in this architecture. Currently, Qt has optional ABI components for ARM and MIPS processors: one component is the main ABI (such as “eabi”, “o32”, “n32”, “o64”); another is whether the calling convention is using hardware floating point registers (“hardfloat” is present). Additionally, if Qt was configured with `-qreal float`, the ABI option tag “qreal_float” will be present. If Qt was configured with another type as qreal, that type is present after “qreal_”, with all characters other than letters and digits escaped by an underscore, followed by two hex digits. For example, `-qreal long double` becomes “qreal_long_20double”.

static PySide6.QtCore.QSysInfo.buildCpuArchitecture()#

Return type:: str

Returns the architecture of the CPU that Qt was compiled for, in text format. Note that this may not match the actual CPU that the application is running on if there’s an emulation layer or if the CPU supports multiple architectures (like x86-64 processors supporting i386 applications). To detect that, use currentCpuArchitecture() .

Values returned by this function are stable and will not change over time, so applications can rely on the returned value as an identifier, except that new CPU types may be added over time.

Typical returned values are (note: list not exhaustive):

“arm”

“arm64”

“i386”

“ia64”

“mips”

“mips64”

“power”

“power64”

“sparc”

“sparcv9”

“x86_64”

See also

buildAbi() currentCpuArchitecture()

static PySide6.QtCore.QSysInfo.currentCpuArchitecture()#

Return type:: str

Returns the architecture of the CPU that the application is running on, in text format. Note that this function depends on what the OS will report and may not detect the actual CPU architecture if the OS hides that information or is unable to provide it. For example, a 32-bit OS running on a 64-bit CPU is usually unable to determine the CPU is actually capable of running 64-bit programs.

Values returned by this function are mostly stable: an attempt will be made to ensure that they stay constant over time and match the values returned by QSysInfo::builldCpuArchitecture(). However, due to the nature of the operating system functions being used, there may be discrepancies.

Typical returned values are (note: list not exhaustive):

“arm”

“arm64”

“i386”

“ia64”

“mips”

“mips64”

“power”

“power64”

“sparc”

“sparcv9”

“x86_64”

See also

buildAbi() buildCpuArchitecture()

static PySide6.QtCore.QSysInfo.kernelType()#

Return type:: str

Returns the type of the operating system kernel Qt was compiled for. It’s also the kernel the application is running on, unless the host operating system is running a form of compatibility or virtualization layer.

Values returned by this function are stable and will not change over time, so applications can rely on the returned value as an identifier, except that new OS kernel types may be added over time.

On Windows, this function returns the type of Windows kernel, like “winnt”. On Unix systems, it returns the same as the output of uname -s (lowercased).

Note

This function may return surprising values: it returns “linux” for all operating systems running Linux (including Android), “qnx” for all operating systems running QNX, “freebsd” for Debian/kFreeBSD, and “darwin” for macOS and iOS. For information on the type of product the application is running on, see productType() .