Companion PEPs 823 and 824 force the community to weigh everyday ergonomics against teaching cost, precedence surprises, and sentinel interactions under Steering Council scrutiny.
By segfaultAuthors will ship a reference build outside main after Steering Council feedback raised the bar for keeping the experiment in-tree.
By segfaultThe ?? and ??= forms would supply defaults only when a value is None, and can be accepted independently of related None-aware access syntax.
By segfaultThe draft splits long-running PEP 505 ideas so access operators can be judged apart from coalescing ones.
By segfaultPEPs 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 rvaluePEPs 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 segfaultA single from-import form would also append names to __all__, targeting the double-entry tax that package facade modules pay today.
By segfaultMark Shannon’s plan would require explicit sharing of objects across threads, building on free-threading work with runtime checks and freezing.
By rvalueBarry Warsaw’s draft would keep __all__ aligned with names marked public, drawing on a decade of atpublic practice.
By rvalueGuido van Rossum and core developers clash over how visibly modules should opt into restricting their public API.
By rvalueA 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