CPython eases Rust requirements as assimilation continues

The maintainers of CPython, the reference implementation of Python, have decided not to make Rust a required dependency. Instead, they are focusing on creating an optional Rust API for internal Python development. This decision came after concerns were raised about the practicality of making Rust a mandatory dependency. Tomáš Šedovič, Rust Programming Manager, explained at RustConf that this approach avoids many of the concerns raised by the community.

The idea of incorporating Rust into Python was initially floated last November by Python programmer Emma Smith, but the proposal was later adjusted to allow for optional Rust extension modules. This change was welcomed by Python creator Guido van Rossum, who saw it as a pragmatic approach to gradually integrating Rust into Python.

Work has been ongoing to develop a Rust API that allows Rust crates to be used in building Python, with the goal of including this in the 3.16 release slated for October 2027. Python and Rust will need to make adjustments to work together, including support for GCC on obscure platforms and ensuring memory safety between the two languages.

Python may also adopt some innovations from Rust, such as the Cargo build system. Despite these changes, CPython's revised approach avoids the aggressive push towards making Rust the sole language for Python, maintaining the flexibility to use Rust selectively.