I'm hardly an expert, but AFAIK CPython's start-up issues are more due to a mix of architectural issues and the fact that it's hard to optimize imports while maintaining backwards compatibility with Python's dynamism. -- Ryan (ライアン) Yoko Shimomura, ryo (supercell/EGOIST), Hiroyuki Sawano >> everyone else https://refi64.com/ On May 3, 2018 1:37:57 AM Glenn Linderman <v+python at g.nevcal.com> wrote: > On 5/2/2018 8:56 PM, Gregory Szorc wrote: >> Nobody in the project is seriously talking about a complete rewrite in >> Rust. Contributors to the project have varying opinions on how >> aggressively Rust should be utilized. People who contribute to the C >> code, low-level primitives (like storage, deltas, etc), and those who >> care about performance tend to want more Rust. One thing we almost >> universally agree on is that we want to rewrite all of Mercurial's C >> code in Rust. I anticipate that figuring out the balance between Rust >> and Python in Mercurial will be an ongoing conversation/process for >> the next few years. > Have you considered simply rewriting CPython in Rust? > > And yes, the 4th word in that question was intended to produce peals of > shocked laughter. But why Rust? Why not Go? http://esr.ibiblio.org/?p=7724 > > > > ---------- > _______________________________________________ > Python-Dev mailing list > Python-Dev at python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > https://mail.python.org/mailman/options/python-dev/rymg19%40gmail.com >
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4