• Sources: primary, discussion
  • Summary: The Python Insider writeup by Seth Larson, dated 2026-09-30, records David Hewitt presenting for a team led by core developers Kirill Podoprigora and Emma Smith, authors of a Rust for CPython PEP draft, with a timeline of a PEP defining success criteria in late 2026, an optional Rust zlib backend and a private Rust API in Python 3.16 in October 2027 with the C code kept as a fallback, io, json, xml, memoryview and the parser in 3.17 in October 2028, and a required Rust build with a public Rust API in October 2029 or later. zlib was chosen because zlib-rs is already used by Firefox, uv, and Cargo, and because zlib is widely used by Python packaging, so almost every pip install in 3.16 would be sped up if the proposal is accepted. Nothing is accepted: Pablo Galindo Salgado called reaching for Cargo dependencies a potential showstopper given that CPython vendors a selective dependency set, Hewitt answered that sources would be vendored so building CPython would not require Cargo, and Hewitt also said it would be disingenuous to claim Rust stays optional forever.
  • Why it matters: CPython now has a dated path toward requiring a Rust toolchain to build, which every distributor and platform packager has to plan against.
  • Follow-up: Watch for the Rust for CPython PEP and whether the optional zlib backend lands in Python 3.16.