Python 3.14.1 was released on December 2, 2025, as the first maintenance release in the Python 3.14 series. It is not a new feature release: the major language and runtime capabilities belong to Python 3.14.0. Instead, this update focuses on bug fixes, build improvements, documentation changes, and security-related corrections.
For teams already running Python 3.14, the release provides a reason to review the complete changelog, test workloads that process untrusted input, and update artifact-verification procedures. The release is available for macOS, Windows, Android, and source builds, although the available packages and platform details differ.
What changed in Python 3.14.1
According to the official Python announcement and the Python 3.14.1 release page, the update contains around 558 bug fixes, build improvements, and documentation changes since Python 3.14.0.
The version-specific Python changelog also includes a SECURITY section. Among the documented changes are protections against potential memory denial-of-service conditions in http.client and plistlib when processing untrusted input. Other security-related corrections involve ZIP64 record consistency, HTML parsing, HTTP parameter parsing, os.path.expandvars(), and sqlite3 behavior.
The supplied release information does not provide a complete summary of all approximately 558 changes, and it does not include CVE identifiers or severity ratings for every security-related correction. Developers should therefore consult the full official changelog rather than treating the examples above as an exhaustive list.
Python 3.14 features remain the broader context
Because 3.14.1 is a maintenance release, it retains the feature context introduced by Python 3.14. That context includes template string literals, deferred annotation evaluation, multiple interpreters, compression.zstd, and the external debugger interface.
The release materials also identify an experimental JIT compiler in official macOS and Windows Python 3.14 binaries. A newer compiler-dependent interpreter can be built from source as an opt-in capability. The supplied documentation does not establish that the JIT is enabled by default, production-ready, available on every platform, or appropriate for a particular workload. Teams should treat it as experimental and validate it separately rather than making it part of a routine maintenance upgrade.
Installers and supported distribution options
The official 3.14.1 release page lists macOS installers, Windows installers and embeddable packages, Android packages, source tarballs, checksums, Sigstore metadata, and software bills of materials for some artifacts.
- The macOS installer supports macOS 10.15 and later and is distributed as a
.pkgpackage. The macOS installation process also includes a separateInstall Certificates.commandstep for installing SSL root certificates. - Windows downloads include 64-bit and 32-bit installers, as well as an ARM64 installer marked experimental. Windows embeddable packages are also available.
- Android artifacts include aarch64 and x86_64 packages.
- Source distributions are available for teams that build Python themselves or need a source-based configuration.
The Python Install Manager is the recommended Windows distribution mechanism. Official Windows documentation describes installing it from the Microsoft Store or from python.org, then using the python, py, and pymanager commands to launch and manage runtimes. The traditional installer remains available throughout the Python 3.14 and 3.15 releases.
For project isolation on Windows, the official documentation recommends a virtual environment for each project. A basic environment can be created with:
python -m venv <env path>Artifact verification has changed
Python 3.14 and later no longer provide PGP signatures for release artifacts. The project recommends using Sigstore instead. The Python 3.14.1 release page provides checksums and Sigstore links, with SBOM links available for multiple artifacts.
Administrators with download or software-supply-chain checks in place should review their verification workflows before adopting the new release. Do not assume that an existing process based on PGP signatures will apply to Python 3.14.1; use the checksums and Sigstore metadata provided on the official release page.
Source-build considerations
Teams building Python from source should review the official configuration documentation. The documented baseline requirements include a C11 compiler, thread support, and IEEE 754 and NaN support. On Windows, the requirements specify Microsoft Visual Studio 2017 or later.
Optional standard-library modules may require additional development dependencies. The documented examples include OpenSSL, SQLite, Tcl/Tk, zlib, and zstd, depending on the modules being built. In particular, compression.zstd may require zstd development support.
The available documentation pages for Windows, macOS, and build configuration are labeled as Python 3.14.7 documentation. They are useful as official Python 3.14-series guidance, but they should not be treated as a complete Python 3.14.1-specific compatibility matrix.
What you should do
- Review the full changelog. The release contains around 558 changes, and the available summary does not enumerate all of them. Check the official changelog for changes relevant to your runtime, libraries, build process, and deployment environment.
- Test untrusted-input paths. Pay particular attention to code that handles HTTP messages, plist data, ZIP records, HTML, HTTP parameters, path expansion, or SQLite behavior. The release documents security-related corrections in these areas, but the supplied sources do not provide a complete exploitability or severity assessment.
- Run compatibility tests before switching production runtimes. The supplied evidence does not provide a complete third-party package or extension-module compatibility matrix, so validate application dependencies and native extensions in a staging environment.
- Verify the downloaded artifact. Use the checksums and Sigstore metadata linked from the official Python 3.14.1 release page, especially if your organization verifies binaries before deployment.
- Use an appropriate installation method. Select the macOS, Windows, Android, or source distribution that matches the target platform. On Windows, consider the Python Install Manager and create a project-specific virtual environment.
- Keep the experimental JIT separate from the maintenance upgrade. If you evaluate it, treat that as a distinct, workload-specific experiment. The supplied sources do not document its complete activation requirements, default status, or production characteristics.
Availability and upgrade caveats
Python 3.14.1 is available now from the official release page. The platform coverage is broad, but it is not identical across artifacts: macOS installers target macOS 10.15 and later, Windows offers multiple architectures with ARM64 marked experimental, and Android packages list specific architectures.
There is no supplied dedicated Python 3.14.1 porting guide, and the available sources do not establish that upgrading to this maintenance release requires configuration changes beyond normal installation and compatibility review. For that reason, the safest upgrade plan is to combine the maintenance update with dependency testing, review of the full changelog, and validation of the organization’s artifact-verification process.
