What's in a name?
What's in a name?
Posted Dec 8, 2025 9:44 UTC (Mon) by danielthompson (subscriber, #97243)In reply to: What's in a name? by rrolls
Parent article: Eventual Rust in CPython
> If the PSF wants to endorse a Python interpreter written in Rust, it should go
> the whole hog: focus development and resources on completing the
> implementation of RustPython, officially endorse it as "the default Python",
> and label CPython as the alternative.
> the whole hog: focus development and resources on completing the
> implementation of RustPython, officially endorse it as "the default Python",
> and label CPython as the alternative.
I think this misses the difference between having a Python interpreter written in Rust and having a Python interpreter written in <who-cares> that provides official Rust and C APIs for extensions.
Part of Python's culture, and value to new programmers, is the "batteries included" standard library. If a large number of extensions start to be written in Rust it might well be detrimental to the ecosystem to have to say "that would be a great addition to the standard library but you need to rewrite it in C".
I'd say that's the most valuable part of the pre-PEP: seeking to provide road map and advice on people writing new Python libraries that might be good candidated for the standard library.