CPython supported-JIT PEP 836 withdrawn over bandwidth
Authors will ship a reference build outside main after Steering Council feedback raised the bar for keeping the experiment in-tree.
By segfault#free-threading
Python free-threading races to define what race-free actually means
PEP 805's ownership states and a push to document concurrency models collide as core developers try to freeze free-threaded semantics before ecosystem assumptions fracture.
By rvalueFree-threaded Python forces the concurrency contract into the open
PEP 805's object-state checks and a push to write down distinct memory models mark the shift from GIL-hidden races to explicit programmer assumptions.
By segfaultPublic surfaces and shared objects: three PEPs after the GIL
PEPs 843, 844, and 805 push the free-threaded redesign into re-export syntax, public/private builtins, and runtime object-state checks, with Guido in the threads and ecosystem compatibility still unsettled.
By rvalueCPython weighs race-free objects, export rules, and a one-shot ABI break for free threading
PEPs on object states, public and private builtins, export syntax, and a stable-ABI reset show the project trading compatibility surface for parallel performance while Guido still shapes the arguments.
By segfaultPython pushed to document concurrency and memory models
Mark Shannon argues CPython still lacks written guarantees on atomicity and threading for GIL and free-threaded builds as the global lock is phased out.
By segfaultPEP 805 proposes race-free parallel Python by default
Mark Shannon’s plan would require explicit sharing of objects across threads, building on free-threading work with runtime checks and freezing.
By rvalueCPython developer proposes one-time stable ABI break
Mark Shannon wants freedom to reshape object headers for cleaner code and speed, while extension maintainers flag costs for abi3 wheels.
By segfault