Since 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.

https://www.youtube.com/watch?v=CyI8TBuKPF0

GitHub - mitsuhiko/rye: a Hassle-Free Python Experience

a Hassle-Free Python Experience. Contribute to mitsuhiko/rye development by creating an account on GitHub.

GitHub
@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! 😅

@whynothugo @mitsuhiko one^Wsome reasons I would guess: because on a mac with python from brew, every venv based on a version which got updated, breaks, so you have to rebuild it. And in debian you need extra packages to get a working pip. And sometimes I would like to pin a specific minor version...

The workflow here makes so much sense... I read the pep for "python as package" today, that would basically replace the one used by rye if I understand it correctly.

@jankatins @mitsuhiko If you update your Python version then you need to rebuild your virtualenv anyway because some packages contain binary bits that might not be compatible.
@whynothugo @mitsuhiko in a python minor version update when only using wheels?