Python 3.13 Release News November 2025 — [repack]

In November 2025, the PSF released telemetry data indicating that Python 3.13 delivers an average over Python 3.12 in pure Python workloads. While not the "5x speedup" some hoped for, the stability of the JIT has been remarkable. Notably, memory overhead increased by less than 5%, validating the architectural decision to avoid aggressive optimization profiles.

By November 2025, the Python development team has kept a steady cadence of maintenance releases: python 3.13 release news november 2025

PEP 703 made the Global Interpreter Lock optional. This allowed Python code to run in parallel on multiple CPU cores without the need for multiprocessing workarounds. In November 2025, the PSF released telemetry data

The most headline-grabbing feature of the 3.13 cycle was the inclusion of a JIT (Just-In-Time) compiler. By November 2025, the Python development team has

A lightweight JIT was added in 3.13, enabled via --enable-experimental-jit . By November 2025:

Released in October 2024, Python 3.13 represented a pivotal moment in the language's history. Following the massive user-interface changes of Python 3.12 (which focused on error messages and parser improvements), version 3.13 turned its gaze inward, focusing on performance internals and runtime architecture. This paper analyzes the one-year impact of Python 3.13, specifically focusing on the graduation of the Just-In-Time (JIT) compiler from experimental to stable status, the initial steps toward a GIL-less future via PEP 703, and the removal of "dead batteries" (PEP 594). As we approach the release of Python 3.14, we evaluate whether Python 3.13 successfully bridged the gap between the interpreted dynamic language of the past and the high-performance powerhouse of the future.

For decades, Python has faced criticism regarding performance, largely due to the constraints of the Global Interpreter Lock (GIL) and the overhead of pure interpretation. While projects like PyPy and Cython offered alternatives, the reference implementation (CPython) remained bound by these legacy constraints.