For three days, the discourse was a war room. Some demanded that the no_gil flag be reverted to experimental. Others insisted on a hotfix that would re-enable a lightweight GIL only when loading untrusted C extensions.
But the true test came in late January 2026.
It reads: “To everyone who said Python would never be fast, never be parallel, never grow up: we hope this release serves as a polite but firm disagreement. Now go break things—intelligently.” python 3.13.1 released november 2025
Elena sat in her apartment, the snow falling outside, watching a livestream of PyCon India 2025. A teenager from Bangalore named Kavya was demonstrating how she used Python 3.13.1’s JIT to train a small LLM on a Raspberry Pi 6. The JIT compiled the hot training loops into native machine code on the fly, cutting training time from two days to six hours.
Of course, paradise had a patch note.
“This is it,” her colleague Marcus whispered over their shared Slack channel, his avatar blinking with a gif of a rocket launch. “No more experimental guardrails. No more ‘may cause undefined behavior.’ This is the production hammer.”
# November 2025 changed everything. # Let's see what November 2030 brings. import For three days, the discourse was a war room
She wrote: “We don’t go backward. We patch forward. The GIL was a beautiful constraint for three decades. But we are not constraint-driven anymore. We are capability-driven. Fix the refcount, add the atomic operations, and ship 3.13.2 by Friday.”