Python None operators, LLVM AI policy, Git blame defaults
Python and LLVM led the day's toolchain traffic with large design threads on None-aware operators and AI-assisted submissions. Git and Swift followed with patches and evolution reviews on blame defaults, shallow fetches, plugins, and compile-time conditionals.
PEP 823 None-aware access operators
PEP 823 proposes None-aware ?. and ?[] operators for Python. A 71-message thread on discuss.python.org, with Guido van Rossum participating, debates design choices and None propagation rules. The change would reshape everyday null handling if accepted.
LLVM RFC to forbid AI-generated communication
An LLVM RFC proposes banning AI-generated or substantially assisted text in pull requests and RFCs. Supporters argue the rule would cut reviewer load from low-quality automated submissions. The 76-message discussion on discourse.llvm.org shows rising friction over machine-written contributions in core projects.
Git blame defaults to .git-blame-ignore-revs
A patch series makes git-blame read .git-blame-ignore-revs by default, with security limits and working-tree access. The change aligns the CLI with forge behavior. Blame users would see more consistent history across tools.
LLDB external language plugin API
An LLDB maintainer proposes a semi-stable external language plugin API. Early interest has come from Carbon, Rust, and Fortran developers. The interface would let out-of-tree languages plug into the debugger without tight coupling.
Pre-PEP dependency sources in pyproject.toml
A Pre-PEP adds a [sources] table to pyproject.toml to standardize dependency redirection. uv, hatch, poetry, and PDM already ship similar mechanisms. A common format would reduce packaging fragmentation for alternate indexes and path overrides.
Swift SE-0554 deployment target conditionals
Swift Evolution is reviewing SE-0554 for deployment-target conditionals that enable compile-time type selection. Discussion centers on behavioral differences between Bazel and SwiftPM. The feature affects how multi-platform code picks APIs at build time.
Swift relaxed floating-point operators
A Swift evolution proposal introduces relaxed operators such as &+ and &* on Float. They would permit algebraic reordering for lower latency. Numerical code could trade strict IEEE semantics for speed.
Git limited fetch for shallow clones
A patch series adds remote.