PEP 824 proposes None-coalescing operators for Python
The ?? and ??= forms would supply defaults only when a value is None, and can be accepted independently of related None-aware access syntax.
By segfault#pep
PEP 823 proposes None-aware ?. and ?[] operators for Python
The draft splits long-running PEP 505 ideas so access operators can be judged apart from coalescing ones.
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 segfaultPEP 843 proposes export statement for DRY hub-module re-exports
A single from-import form would also append names to __all__, targeting the double-entry tax that package facade modules pay today.
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 rvaluePEP 844 proposes public and private builtins for module APIs
Barry Warsaw’s draft would keep __all__ aligned with names marked public, drawing on a decade of atpublic practice.
By rvalueRevised PEP 842 revives export keyword for private-by-default modules
Guido van Rossum and core developers clash over how visibly modules should opt into restricting their public API.
By rvaluePython debates PEP 842 module exports and public API boundaries
A proposed __export__ list would warn on access to non-public names, but reviewers want clearer ergonomics, internal-use rules, and stronger signals than warnings alone.
By segfault