“In the past, a December patch would have been risky,” said Vance, sipping a lukewarm mug of glögg. “But we designed 3.13 to be patchable . The JIT, the no-GIL mode… they’re modular. 3.13.1 proves we can move fast and fix things fast without breaking the 2,000,000 packages on PyPI.”
And what a patch it was.
“This isn’t a feature drop,” said Elena Vance, a release coordinator based in Berlin, in an exclusive interview. “3.13.0, which came out in October, was the big show—the new incremental garbage collector, the experimental JIT compiler hooks, and the long-awaited ‘no-GIL’ build flag. 3.13.1 is the stabilizer . It’s the patch that makes sure those brave early adopters don’t wake up on Christmas morning with a broken CI pipeline.” python 3.13.1 released dec 2025
The core team’s Slack channel finally went quiet. The last message of the night, from a release engineer in San Francisco: “3.13.1 wheels are green on all platforms. Go home. Merry Christmas. And for the love of Guido, do not look at the issue tracker until Jan 4.” “In the past, a December patch would have
December 3, 2025 – Brussels, Belgium
The real story, however, wasn't the bugs. It was the process . Python 3.13.1 was the first minor release to fully utilize the new “Frozen Core” CI system—a massive rewrite of the build automation that cut the release testing time from 18 hours down to 90 minutes. 2025 – Brussels