Python 3.14.7 Ships a Routine Maintenance Release
The seventh point release on the 3.14 line rolls up nearly 500 bugfixes with no new features, alongside a parallel update to the 3.13 line.
On August 5, 2026, the Python core team released Python 3.14.7 alongside Python 3.13.15, the latest maintenance builds on their respective release lines. Maintenance releases like this one don't add language features — they exist to roll up bugfixes, build-system corrections, and documentation updates that accumulated since the previous point release.
3.14.7 is the seventh maintenance release since Python 3.14.0 shipped, and the changelog credits roughly 499 individual fixes from 86 contributors since 3.14.6. That volume is typical for an actively maintained release line still early in its support window — 3.14 will keep receiving frequent bugfix releases like this one before eventually moving to security-only maintenance.
Notable fixes in this release touch libexpat (the XML parsing library Python bundles), HTTP credential-scoping behavior, SSL context callback handling, zlib decompression, sqlite3 cursor attribute bugs, and ctypes pointer handling — a spread across networking, compression, and C-extension code that's typical of a general maintenance sweep rather than a targeted security patch.
None of this touches the headline features that shipped with 3.14.0 itself: PEP 779's official support for free-threaded (no-GIL) builds, PEP 649's deferred evaluation of annotations, PEP 750's template strings, PEP 734's support for multiple interpreters from the standard library, and a new compression.zstd module. Those land once, in the .0 release; every .x release after that is fixes only.
One release-process detail worth flagging for teams that verify downloads: starting with 3.14, Python no longer ships PGP signatures for release artifacts, relying on Sigstore for supply-chain verification instead. A build pipeline that still checks for a .asc signature file needs to switch to Sigstore verification.
Full release notes, including the complete list of fixed issues, are published on python.org alongside every release; teams running 3.14 or 3.13 in production should update to 3.14.7 or 3.13.15 on their normal patch cadence.