CPython JIT PEP withdrawn, ClangIR defaulted, Python security releases
Python's Steering Council pre-submission feedback led to withdrawal of a JIT PEP, while the Clang area team accepted enabling ClangIR by default and CPython shipped expedited security releases across five branches. Separate threads covered formal verification of Julia Base, multi-version Swift packages, Git fetch and branch options, and glibc loader hardening.
PEP 836 for CPython JIT withdrawn after Steering Council feedback
PEP 836, which described a path to a supported JIT compiler for CPython, was withdrawn after pre-submission feedback from the Steering Council. The discuss.python.org thread that followed drew 27 participants across 42 messages and turned heated over process transparency, funding, and motives. Developers tracking CPython performance and governance will note both the withdrawal and the open questions left around JIT support.
Clang area team enables ClangIR build by default
The Clang area team accepted an RFC to enable the ClangIR build, together with MLIR, by default. The -DCLANG_ENABLE_CIR=Off CMake option remains supported for builds that must keep it off. The change makes IR infrastructure more consistently available to developers working on Clang-based tools and optimizations.
Expedited Python releases block compromised CA keys
Maintainers issued Python 3.15.2, 3.14.10, 3.13.18, 3.12.16, and 3.11.18 as expedited releases. The updates block compromised eMudhra CA keys inside the ssl module to protect pip installs. Users on any of the five supported branches should upgrade to reduce certificate risk during package installation.
Lean 4 model of Julia Base reports over 400 bugs
A discourse.julialang.org thread discussed formally modeling Julia Base with Lean 4 and reported finding more than 400 bugs. Participants debated how specifications should be maintained alongside the implementation. The work highlights both defects in Base and the ongoing cost of keeping formal models current.
SwiftPM pitch for multiple major package versions
A pitch on the Swift forums proposes allowing multiple major versions of one package inside a single resolved dependency graph. The change would address diamond dependency failures that currently break resolution. Package authors and application developers who hit version conflicts would gain more flexible graphs if the idea advances.
Git config to limit fetches from shallow remotes
A patch series on the Git mailing list adds remote.
Git --delete-merged detection of squash merges
A patch series proposes extending git branch --delete-merged so it can detect branches that were squash or rebase merged. The maintainer requested that any such behavior be available only behind an opt-in flag. The series would ease branch cleanup after common non-fast-forward workflows if accepted in that form.
glibc loader hardening tunables
A thirteen-part patch series for glibc adds rtld hardening tunables such as require_pie, refuse_textrel, and bind_now, and raises some security defaults. The tunables give administrators finer control over loader policy. Distributions and projects that ship or embed glibc may review the new defaults and override options.