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.
commit 9f1c2b8d9e (HEAD -> main, tag: v4.0.0) Author: Guido van Rossum <guido@python.org> Date: Tue Nov 30 23:59:58 2025 +0000 python release november 30 2025
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. It started as a quiet Tuesday in a
She took a sip of her now‑cold coffee, glanced at the wall of sticky notes that chronicled the months of debate, and opened the file that had been her secret diary for the release: . Chapter 1 – The Whisper of “Self‑Aware” Two years earlier, in a cramped coffee shop in Nairobi, a young researcher named Kofi had posted a pre‑print about “Self‑Aware Python Objects” . The idea was simple: objects could introspect not just their own state, but the intent behind the code that manipulated them, using a lightweight provenance system. The paper sparked a firestorm of excitement and dread. “Too magical,” some warned. “Exactly what we need,” others argued. Instead of a global lock, each bytecode operation