Does this have faster startup times than cpython? Every time I want to rewrite a shell function in python, I always hesitate due to the slow startup.
I curious why you would think so, since CPython is already written in C
RustPython: A Python Interpreter Written in Rust
71–75 of 75 posts
Re: RustPython: A Python Interpreter Written in Rust
#72Does this have faster startup times than cpython? Every time I want to rewrite a shell function in python, I always hesitate due to the slow startup.
I curious why you would think so, since CPython is already written in C
Well CPython has a lot of backwards compatibility to deal with that RustPython doesn't, so "import subprocess" might result in very different behavior.
Re: RustPython: A Python Interpreter Written in Rust
#73There's no installable version for pyenv. In general, how well does this work with virtualenvs?
Re: RustPython: A Python Interpreter Written in Rust
#74https://notes.eatonphil.com/lua-in-rust.html
It's some kind of developer trend.
Re: RustPython: A Python Interpreter Written in Rust
#75Earlier quoted context omitted.
Eh. Once you start using imports, python slows down dramatically. So I guess it really just depends what your scripts use.
Regarding import cost, as it’s doing heavy IO traversing the file system, the cost heavily depends on how fast you can do IO in the hardware, and also the file system (and the OS). So a fast SSD will help, and somewhat surprisingly putting it inside docker helps (in an HPC context, not so sure it’s implications here as we’re talking about a short scripts.) But the context here is to port shell scripts to Python, I’m…
>But the context here is to port shell scripts to Python, I’m not sure how huge amounts of imports matters.
Never question the modern developers ability to import 1500 heavy libraries to accomplish something that only takes 10 lines of code.