However, critical context must be noted: free-threading is . Official installers from python.org do not enable this feature. To obtain a no-GIL build, developers must compile CPython 3.13 from source with the --disable-gil configuration flag. Even when enabled, the Python Steering Council warns that this mode may cause unexpected problems, and production use is strongly discouraged at this stage.
The future of Python is clearly multi-threaded and JIT-compiled. Python 3.13 lights the path—but the destination is still one or two releases away.
For CPU-bound, multi-threaded workloads, this could remove the GIL bottleneck. However, the default build still uses the GIL. Expect performance improvements only in specific scenarios, and expect some single-threaded slowdowns (10-20% in early benchmarks). python 313 release notes verified
❌ No stable ABI for free-threaded builds. ❌ No automatic GIL removal — you must rebuild Python. ❌ No performance revolution from JIT yet.
Python 3.13 marks the beginning of the end for the GIL by introducing an experimental . However, critical context must be noted: free-threading is
Python 3.13 introduces an based on the "copy-and-patch" technique described by Haoran Xu and Fredrik Kjolstad (Stanford). This is not a high-performance JIT like PyPy’s; instead, it’s a low-effort, low-complexity JIT that compiles small units of bytecode to machine code at runtime.
What dominate your production environment? Even when enabled, the Python Steering Council warns
Microbenchmarks show speedups of 5-25% for pure Python loops and arithmetic. Real-world code sees more modest gains. The JIT is and still under heavy development.
: Standard installers now include the free-threaded binary, typically named python3.13t on Unix-like environments.