Our great sponsors
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
multiversion
A hack that allows you to use different versions of the same library in the same Python process without clashes (by mitsuhiko)
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
The entire shim of rye fits into ~100 lines of Rust code: https://github.com/mitsuhiko/rye/blob/main/rye/src/cli/shim.rs
One interesting tidbit is that it completely ignores your system Python installations, and instead uses precompiled installations of Python by indygreg from PyOxidizer. This means you don't have to deal with installing Python. It just auto downloads the right builds.
what’s different from using https://asdf-vm.com/ ?
I don't see much other than reliance on sys.modules keying that is a hindrance in a better import story, and even that is solvable. Already 12 years ago I showed that loading multiple incompatible versions of a library into the same Python interpreter is possible, and that was a long time before importlib landed which would make some of this easier.
Curious question, since both are written in Rust (thus performance-wise both will be great) what other differences are there between rye and huak ?
There's a project that does this with using Nix: https://github.com/takeda/nix-cde (this is a wrapper around https://github.com/nix-community/poetry2nix)
There's a project that does this with using Nix: https://github.com/takeda/nix-cde (this is a wrapper around https://github.com/nix-community/poetry2nix)
I can immediately see some things rye is doing differently, like keeping the venvs themselves free of pip and pip-tools. I wonder in your explorations if you've tried rtx for managing python installations, or my own zpy wrapper of pip-tools+venv (which can also replace pipx).
I can immediately see some things rye is doing differently, like keeping the venvs themselves free of pip and pip-tools. I wonder in your explorations if you've tried rtx for managing python installations, or my own zpy wrapper of pip-tools+venv (which can also replace pipx).
Now about the second point on the complexity of the shim strategy (cf. the rbenv implementation) with respect to the PATH update strategy (cf. the chruby implementation), what do you think?
Now about the second point on the complexity of the shim strategy (cf. the rbenv implementation) with respect to the PATH update strategy (cf. the chruby implementation), what do you think?