The core team took the biggest technical gamble in a decade—optional no-GIL concurrency and a JIT compiler—and within two months, they delivered a patch that makes those experiments safe to run outside of a jail. If you’ve been waiting for a sign to start testing Python 3.13, this is it.
Barely two months after the landmark rollout of Python 3.13.0—a release that introduced experimental and an optional no-GIL mode —the Python Steering Council and core development team have dropped the first bugfix release of the new series: Python 3.13.1 . python 3.13.1 release date news
“The October release was about possibility,” said one core developer in a discourse post, speaking on condition of background. “The December release is about reliability. If you’re a library maintainer, this is the version you should start testing against for real.” While the full changelog is extensive, three major areas dominate the patch notes. 1. The JIT Compiler (No Longer Crashing on Corner Cases) The experimental copy-and-patch JIT —which translates bytecode to machine code at runtime for modest speedups (5–25% on pure-Python loops)—had several edge-case failures in 3.13.0. Users reported crashes when using pdb (the debugger) with JIT enabled, as well as recursion depth overflows. The core team took the biggest technical gamble