Python 3.14.3 and Python 3.13.12 became available on February 3, 2026, giving teams new maintenance releases within the Python 3.14 and 3.13 feature series. These are not new feature-series launches: they focus on bug fixes, build improvements, and documentation changes while providing updated downloads for supported platforms.
For developers and platform administrators, the releases provide a defined upgrade point for projects already using Python 3.14 or 3.13. However, the supplied release information does not include a complete list of individual fixes or security changes, so compatibility testing and review of the linked changelogs remain important.
What changed in Python 3.14.3 and 3.13.12
Python 3.14.3 is the third maintenance release in the Python 3.14 series. Its official release page describes around 299 bug fixes, build improvements, and documentation changes since Python 3.14.2.
Python 3.13.12 is the twelfth maintenance release in the Python 3.13 series. The corresponding release page reports around 240 changes since Python 3.13.11. The original announcement supplied with this release story describes the figure as around 250, so that number should not be treated as exact. The discrepancy is material when comparing release scope, and the official release page’s approximate figure is the more specific reference for the 3.13.12 release page.
The release pages link to the detailed maintenance changelogs, but the individual entries were not available in the supplied material. It is therefore not possible to responsibly identify particular bug fixes, regressions, or security fixes from these releases here.
Available downloads and platform coverage
Python 3.14.3 has official source archives, macOS installers, Windows installers for 32-bit, 64-bit, and ARM64 systems, Windows embeddable packages, Android aarch64 and x86_64 embeddable packages, and a Windows release manifest. The release page lists macOS 10.15 and later, and marks the Windows ARM64 installer as experimental.
Python 3.13.12 provides source archives, a macOS installer, Windows 32-bit, 64-bit, and ARM64 installers, Windows embeddable packages, and a Windows release manifest. Its release information lists macOS 10.13 and later and also identifies the Windows ARM64 installer as experimental.
These inventories establish which release artifacts are published, but they are not a complete system-requirements matrix. The supplied information does not document every operating system, compiler, dependency, or architecture requirement for all installation paths. Teams with specialized build environments should check the release documentation and test their deployment process rather than assuming that an available artifact guarantees compatibility.
Verification metadata is included
Both release pages publish SHA-256 checksums and Sigstore metadata for their listed artifacts. The Python 3.13.12 page also lists GPG signatures. The Python 3.14.3 release information states that Python 3.14 and later no longer provide PGP signatures for release artifacts and points verifiers toward Sigstore.
The available material confirms that verification metadata is published, but it does not provide a complete, release-specific Sigstore verification procedure. Administrators should use the checksums and consult the linked Sigstore resources as part of their existing software-supply-chain process rather than treating the presence of metadata as a substitute for verification.
What this means for Python 3.14 users
Python 3.14 already contains the feature-series changes documented in the Python 3.14 “What’s New” documentation. These include deferred annotation evaluation, template string literals, multiple interpreters in the standard library, compression.zstd, officially supported free-threaded Python, UUID versions 6 through 8, and a safe external debugger interface.
Those capabilities belong to the Python 3.14 feature series and should not be presented as features introduced specifically by maintenance release 3.14.3. The practical reason to evaluate 3.14.3 is the accumulated maintenance work since 3.14.2, not a new feature announcement.
Python 3.14’s new interpreter type is opt-in, requires building from source, and requires certain newer compilers. That path should be evaluated separately from the standard downloadable installers. The supplied release information does not provide a complete compiler or dependency matrix, so teams considering this configuration should validate their toolchain independently against the applicable documentation.
Windows installation and runtime selection
Windows users can obtain the Python Install Manager through the Microsoft Store or from python.org. The Windows installation documentation describes the roles of the python, py, and pymanager commands.
In the documented model, python launches a default runtime, while py can be used for runtime selection and management. The command py -V:<TAG> selects a specific runtime, and pymanager provides an unambiguous manager command. The documentation also describes creating project environments with:
python -m venv <env path>The Windows documentation recommends using a virtual environment for each project. It also states that the default runtime can be overridden through the PYTHON_MANAGER_DEFAULT environment variable or a configuration file. Administrators should test command resolution, PATH behavior, version selection, and virtual-environment creation in their managed images before broad deployment.
What you should do before upgrading
- Review the maintenance changelogs. The release pages link to the detailed changes, which are needed to determine whether a particular fix or behavior change affects your application.
- Match the artifact to the target environment. Check the operating system and architecture, and remember that Windows ARM64 is marked experimental for both releases.
- Verify downloads. Compare downloaded artifacts with the published SHA-256 checksums and incorporate the available Sigstore metadata into your verification process.
- Test applications and extensions. Run project tests against the selected interpreter, including dependencies and native extension modules. The supplied release information does not establish compatibility results for individual projects.
- Use isolated environments. On Windows, evaluate the Install Manager commands and create project virtual environments with
python -m venvas recommended by the documentation. - Check whether you need the feature series or only a maintenance update. If a project is already on Python 3.14 or 3.13, the corresponding maintenance release is the directly relevant upgrade path. A move between feature series requires a broader compatibility assessment.
Availability caveat
The February 3, 2026 announcement establishes when Python 3.14.3 and 3.13.12 became available. The official release pages also state that both versions have since been superseded by later patch releases. Anyone choosing a runtime today should distinguish the historical availability of these releases from the current version recommendation and review the latest applicable Python release information before starting a new deployment.
For existing 3.14 and 3.13 projects, these releases remain useful reference points for understanding the maintenance history and for controlled upgrade testing. The exact fixes that matter to a given application must be determined from the full changelogs and the project’s own test results.
