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 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 segfaultThe attribute would let the compiler enforce at-most-once calls and reason about closure captures alongside non-copyable types.
By segfaultA single from-import form would also append names to __all__, targeting the double-entry tax that package facade modules pay today.
By segfaultGuido van Rossum and core developers clash over how visibly modules should opt into restricting their public API.
By rvalueSE-0539 would let accessor macros promise the compiler that an initializer expression will run only after self is fully available.
By rvalueThe change targets a blocker for public initializers on macro-generated structs without waiting on new synthesis syntax.
By rvalue