Python 3.13.1 Released | November 2025 ^new^

By Christmas Eve, the community had stabilized. The PyPI daily download count for packages marked python_version >= '3.13.1' had tripled. NumPy released 2.5.0 with explicit subinterpreter support, yielding 4x speedups on large matrix multiplications. Even Django’s ASGI server got a patch that let each request handler spin up in its own lightweight subinterpreter, wiping out the last of the global connection-pool bottlenecks.

And on her own laptop, running Python 3.18.4 (the JIT was up to tier 3 by then, and the GIL was a compile-time joke you told at conferences), Elena smiled. She opened a new file, imported interpreters , and wrote the first lines of a program that would simulate a billion neural synapses across sixteen cores. python 3.13.1 released november 2025

A critical CVE was announced—a use-after-free in the new biased reference counter, only triggerable when mixing subinterpreters and C extensions that manually manipulated PyObject* refcounts. The entire Python security team held an emergency sprint. By Christmas Eve, the community had stabilized

The cursor blinked. The code waited. And Python, ancient and newborn all at once, hummed quietly in the silence. End of story. Even Django’s ASGI server got a patch that

- match now supports case with guard: as a native keyword expression. No more parentheses gymnastics. Elena leaned back, her chair creaking. The subinterpreters were the real story. For years, Python had been a single-threaded soul trapped in a multi-core world. You could spawn processes, but they were heavy. You could use asyncio , but it was cooperative. True parallelism—without the GIL’s chaperone—had always been the dream deferred.

- Full standard library support. interp.run() now behaves as predictably as threading . No more "RuntimeError: cannot call daemon thread" surprises.

But the true test came in late January 2026.