…until October 2026, when Python 3.15 promised to eliminate the GIL entirely. (Wait, didn’t they just do that?) Ah, the circle of life.
The Python Steering Council rushed out a hotfix: PYTHON_GIL=1 environment variable to re-enable the old behavior. python updates december 2025
But the writing was on the wall. The future was parallel. On Christmas morning, a mysterious pull request appeared on CPython’s GitHub. …until October 2026, when Python 3
from typing import validated @validated def divide(a: float, b: float) -> float: return a / b …until October 2026
Scrolling down… .
RuntimeError: object '__main__.Ledger' is not thread-safe The docs were clear: "Free-threading requires explicit locking or use of new threading.Lock for shared mutable state." But thousands of old libraries—written assuming the GIL was a shield—now leaked data like a sieve.