The no-GIL or “free-threaded” builds are still considered experimental, so they shouldn’t be deployed in production yet. The Python team wants to alleviate as much of the single-threaded performance impact as possible, along with any other concerns, before giving the no-GIL builds the full green light. It’s also entirely possible these builds may never make it to full-blown production-ready status, but the early signs are encouraging.
Another forward-looking feature introduced in Python 3.13 is the experimental just-in-time compiler or JIT. It expands on previous efforts to speed up the interpreter by generating machine code for certain operations at runtime. Right now, the speedup doesn’t amount to much (maybe 5% for most programs), but future versions of Python will expand the JIT’s functionality where it yields real-world payoffs.
We kissed Python’s “dead batteries” goodbye
Python’s been around for over three decades, and it’s accumulated some cruft across the years. Some of that baggage consists of standard library modules that have fallen into obsolescence or are no longer actively maintained. Since Python is described as a “batteries-included” language, these aging modules have been called dead batteries.
