Python PEPs, glibc linker CVEs, Rust LTS

Python advanced proposals on parallel safety and builtins while glibc published two ld.so advisories. Rust and Julia communities argued over long-term support policy and LLM-generated posts.

PEP 805 proposes safe parallel Python

A new PEP 805 introduces runtime checks and object states intended to enable race-free parallel execution in Python. The work builds directly on PEP 703 and PEP 734. Developers interested in concurrent Python without data races will want to follow the discussion.

Glibc publishes CVE-2026-95818 advisory

The glibc project committed an advisory for CVE-2026-95818, a buffer overflow in ld.so that affects setuid programs. The vulnerability spans versions 2.14 through 2.44. Maintainers of setuid binaries should assess exposure and apply updates promptly.

Glibc publishes CVE-2026-86805 advisory

Glibc also released an advisory for CVE-2026-86805 describing a TOCTOU race in ld.so $ORIGIN handling on AT_SECURE binaries. The issue can undermine secure execution contexts that rely on origin-relative paths. The disclosure pairs with the related buffer-overflow fix and continues linker hardening efforts.

PEP 844 adds public and private builtins

A 151-message thread with 34 participants examines PEP 844, which would introduce public and private builtins to control all. Guido van Rossum took part in the exchange. The change would give library authors more precise tools for namespace export management.

Pre-RFC for official Rust toolchain LTS

An extensive pre-RFC on the Rust internals forum proposes an official LTS toolchain together with an MSRV policy. The 130-message discussion involving 33 participants shows a sharp divide between concerns over stagnation and the need for better ecosystem support. The result could reshape how dependent projects pin and maintain Rust toolchains.

PEP 823 proposes None-aware operators

PEP 823 revives optional chaining by proposing None-aware ?. and ?[] operators. The short 17-message thread with 15 participants continues a long-running debate on the feature. Adoption would bring Python closer to null-safe access idioms used in other languages.

Glibc office hours debate infrastructure move

Meeting minutes from glibc office hours record heated discussion of a possible migration to OpenSSF and LF IT infrastructure, consensus processes, and earlier sourceware service disruptions. Thirteen participants produced 68 messages. The exchange surfaces ongoing governance questions around project hosting and operational reliability.

Julia forum debates LLM post policy

A 159-message thread with 40 participants on the Julia discourse arose after a package announcement prompted calls for auto-deletion of LLM-generated posts. Contributors voiced strong reluctance to read such material. The dispute highlights emerging norms around AI-generated content in open-source community forums.