Python 3.14 released — free‑threaded Python supported, subinterpreters, Sigstore and experimental JIT

PythonDevOpsBackend

Key update

Python 3.14.0 (final) shipped on 2025‑10‑07 with several changes that materially affect production developers: the free‑threaded (GIL‑less) build is now officially supported (phase II of PEP 703 / PEP 779), deferred evaluation of annotations (PEP 649), multiple interpreters available from the standard library (PEP 734), a new Python C configuration API (PEP 741), a built‑in Zstandard compression module, official Android binaries, and experimental JIT‑equipped macOS/Windows release binaries. The release also removes PGP signatures for release artifacts in favor of Sigstore verification. (python.org)

Why it matters

This is one of the most practically consequential Python releases in years. Free‑threaded Python moving to “supported” signals that real concurrent multithreaded workloads (and the ecosystem changes required for them) are now a supported path — but it also means maintainers of C extensions and binary wheels must test and, where necessary, update thread‑safety and ABI assumptions. Subinterpreters in the stdlib provide a safer low‑overhead isolation primitive for concurrency and embedding (useful for language servers, plugin hosts, and some server architectures). The Sigstore move changes release verification in CI/CD and distribution workflows — teams should adopt Sigstore verification or tooling rather than relying on old PGP workflows. The experimental JIT and official Android binaries lower the bar for mobile and desktop performance experimentation, but they’re explicitly experimental: measure before relying on them in production. Finally, there are compatibility notes (e.g., changes around multiprocessing start methods on non‑macOS/Windows platforms) that can surface as pickling or process‑start regressions in existing deployments; test your CI, wheels and container images against 3.14. (python.org)

Source

Read Next