Skip to main content

Evidence, not slogans

QZX compatibility status

QZX's automated tests are based on Microsoft Windows Server 2025 (10.0.26100) (x64), Microsoft Windows Server 2025 (10.0.26100) (x64 host / x86 CPython), Microsoft Windows Server 2022 (10.0.20348) (x64), Microsoft Windows 11 Enterprise (10.0.26200) (arm64), Ubuntu 24.04.4 (x64), Ubuntu 24.04.4 (arm64), Ubuntu 22.04.5 (x64), macOS 26.4 (25E246) (arm64), macOS 15.7.7 (24G720) (arm64), macOS 15.7.7 (24G720) (x64 (Intel)), Debian 13.6 (amd64), Alpine Linux 3.24.1 (x86_64), FreeBSD 15.1-RELEASE (amd64), OpenBSD 7.9 (amd64), OmniOS r151054 LTS (x86_64), and Oracle Solaris 11.4 CBE (x86_64), using the standard CPython 3.13 build.

Visual overview of Windows, Linux and macOS platform cards with distinct indicators for evidence, supported scope, host dependencies and visible limitations.
Observed evidence Supported scope Host-dependent factors Visible limitations
This is an orientation aid, not a scorecard. The generated environment table and each command page remain the source of record for exact platform claims.

Published package

PyPI 0.2.2.0.8

Released 8 September 2026. PyPI declares Python >=3.11 and “OS Independent.” Those metadata fields describe packaging intent; they are not a cross-platform test report.

Development checkout

Alpha 0.2.2.0.8

The website catalog is generated from this checkout. Command pages reconcile it with the published 0.2.2.0.8 wheel and make any development-only capability explicit.

Installation environments

Use pip where you control Python; use pipx when you want isolation

python -m pip install --upgrade qzx remains the shortest route inside a Python environment you intentionally control. For QZX as a standalone CLI, pipx install qzx keeps its dependencies isolated. If a base interpreter reports externally-managed-environment, prefer pipx or your platform's supported package tooling instead of forcing that interpreter with --break-system-packages.

Already have pipx and just want to evaluate QZX? pipx run --spec qzx qzx version runs the published package without keeping a QZX installation. See the complete QZX installation guide.

Automated test environments

This table is generated from the same source used by the repository README and the package description prepared for future PyPI publications.

Platform and versionArchitectureGitHub Actions configuration
Microsoft Windows Server2025 (10.0.26100)x64Windows Server 2025 x64
Microsoft Windows Server2025 (10.0.26100)x64 host / x86 CPythonWindows Server 2025 x64 with x86 CPython
Microsoft Windows Server2022 (10.0.20348)x64Windows Server 2022 x64
Microsoft Windows11 Enterprise (10.0.26200)arm64Windows 11 Enterprise ARM64
Ubuntu24.04.4x64Ubuntu 24.04 x64, ubuntu-24.04
Ubuntu24.04.4arm64Ubuntu 24.04 ARM64
Ubuntu22.04.5x64Ubuntu 22.04 x64
macOS26.4 (25E246)arm64macOS 26 ARM64
macOS15.7.7 (24G720)arm64macOS 15 ARM64
macOS15.7.7 (24G720)x64 (Intel)macOS 15 Intel
Debian13.6amd64Debian 13.6 amd64
Alpine Linux3.24.1x86_64Alpine Linux 3.24.1 amd64
FreeBSD15.1-RELEASEamd64FreeBSD 15.1-RELEASE amd64
OpenBSD7.9amd64OpenBSD 7.9 amd64
OmniOSr151054 LTSx86_64OmniOS r151054 LTS x86_64
Oracle Solaris11.4 CBEx86_64Oracle Solaris 11.4 CBE x86_64

QZX is Alpha software. This list identifies the environments used by the test matrix; it does not report run outcomes or guarantee compatibility.

Python versions

QZX supports standard CPython 3.11 or newer. Its cross-platform certification matrix uses standard CPython 3.13.x; experimental free-threaded CPython builds, PyPy, and other implementations are not certified.

Published PyPI 0.2.2.0.8 declares Python >=3.11. The 0.2.2.0.8 development checkout independently requires Python >=3.11. The test matrix above uses the standard CPython 3.13 build; its source is checked against the configured GitHub Actions workflows.

Host-dependent capabilities

Commands may depend on permissions, platform utilities, network access, Git, language toolchains, formatters, psutil, python-magic, or smartmontools. Missing optional tools should produce explicit failure context, but capability parity is not guaranteed.