"It's a pre-PEP because official Python proposals are called PEPs, short for Python Enhancement Proposals. The idea has been bruited by two core Python developers, Emma Smith and Kirill Podoprigora, who write: Rust will initially only be allowed for writing optional extension modules, but eventually will become a required dependency of CPython and allowed to be used throughout the CPython code base."
"The post is very readable, and it addresses several of the more obvious objections. For example, it lists the 20 core platforms that CPython officially supports, and notes that all have some level of Rust support - although 11 of them are Tier 3 platforms for Rust. It also creates an interesting cyclic dependency for bootstrapping the Python interpreter: building Rust from scratch depends on Python."
Proposal recommends allowing Rust into CPython, initially for optional extension modules and ultimately as a required dependency across the entire codebase. Twenty core CPython platforms are listed, with every platform showing some Rust support, though eleven are classified as Tier 3 for Rust. A bootstrap cyclic dependency emerges because building Rust from scratch depends on Python, creating mutual prerequisites on fresh systems. Several CPython-supported platforms lack Rust support, including RISC OS, HP PA-RISC, Mac OS X on PowerPC, and CentOS Linux 6. Multiple Python implementations exist, including RustPython and many CPython variants. Debian's move to require Rust for APT raises similar compatibility concerns.
Read at Theregister
Unable to calculate read time
Collection
[
|
...
]