It started as a quiet Tuesday in a cramped apartment on the 7th floor of a converted warehouse in Rotterdam. Outside, the wind that had been whipping the Dutch canals for weeks finally calmed, and the sky took on that soft, pale‑blue hue that programmers swear is the perfect background for a new idea.
The core team, after weeks of heated mailing‑list threads, decided to embrace the concept—not as a black‑box sorcery, but as a transparent, optional layer. The result was the module, a modest library that could be imported with a single line: python release november 30 2025
Thanks to the community for 15 years of patient, brilliant feedback. This release is yours. Maya closed the terminal, the cursor now a steady, satisfied blink. She leaned back, eyes drifting to the window where the wind had finally settled. Below, a line of cyclists whizzed past, their helmets glinting like tiny, moving comments in a script. It started as a quiet Tuesday in a
commit 9f1c2b8d9e (HEAD -> main, tag: v4.0.0) Author: Guido van Rossum <guido@python.org> Date: Tue Nov 30 23:59:58 2025 +0000 The result was the module, a modest library
* Add cooperative-multicore scheduler (PEP 734) * Introduce intent module for provenance (PEP 738) * Update docs with narrative-driven examples * Bump version to 4.0.0
In early 2025, a collaboration between the core team and the European Space Agency’s onboard‑computing group produced a proof‑of‑concept: . Instead of a global lock, each bytecode operation carried a tiny credit token that could be passed between threads. If a thread needed to execute a block that required more than its current credit, it would politely yield, letting the scheduler re‑balance the load.