Armin RonacherSince quite a few people asked me about my **rye** "package solution" for Python, I put it on GitHub. https://github.com/mitsuhiko/rye — it's written in Rust and just wraps pip/pip-tools and virtualenv. Also auto installs Python for you. It's a bit of my dream of what Python packaging could be.
Hugo 雨果@mitsuhiko Why can't it just use the distribution's Python? What kind of distro is missing a binary python package? I feel like we're living in different universes! 😅
poswald@whynothugo @mitsuhiko I would personally flip this from “why can’t it just use…” to “why not isolate to a known…” For that reason I think this is the right choice for a long-lived project. It’s not about having a python available in the distro as much as it’s about exerting more control over your env.
@poswald @mitsuhiko I'm not sure I fully understand the use case. You want to indefinitely maintain a specific version of Python (e.g.: the one you'd use on production), but you're fine with all other dependencies (e.g.: anything that's not python or python packages) being updated?
I've worked on projects where a specific python was desirable to match production, but usually using docker of a VM was the solution because it made sense to pin everything else too.
@whynothugo @mitsuhiko ah ok. Yeah if the solution is docker then you’re grabbing control at a lower level. You just need one clean way to install on your chosen OS that works. Hopefully it doesn’t break too much from version to version. That’s not a bad thing but it’s also understandable why people who operate at the language level want more consistent control of their envs.
@mitsuhiko @poswald Yeah, that makes sense. I mostly can't imagine what kind of project requires such fine grained control for a single dependency but is completely flexible with all others.