NEW YORK — What happened: Python 3.15 has arrived with continued refinements to the experimental free-threaded build mode (PEP 703), allowing developers to run multithreaded Python code without the traditional Global Interpreter Lock (GIL) bottleneck.
Why it matters: Python has long dominated data science, scripting, and web development, but its inability to utilize multiple CPU cores effectively within a single process forced developers to rely on complex multiprocessing libraries. Free-threaded Python promises true multi-core execution for standard threads.
Deep dive: Running code without the GIL requires thread-safe reference counting and atomic operations, which historically added a single-threaded performance tax of up to ten percent. Python 3.15 introduces specialized optimizations that narrow this performance penalty to under three percent for typical workloads, making it increasingly viable for production web servers.
Report check: Claims vs what is verified vs still rumor. It is verified that standard library modules are progressively adding thread-safety guarantees. Rumors that C-extension compatibility is already at 100 percent are false; many popular binary packages still require specific patches to run safely without the GIL.
Open questions: When will major Linux distributions ship the free-threaded build as the default Python package, and how long will the ecosystem take to update older C-extensions?