> use of venvs for Python all the time Ah I think that's why then. Venvs are IMO the best of every example I've given. When you make one, Python is embedded in

> use of venvs for Python all the time Ah I think that's why then. Venvs are IMO the best of every example I've given. When you make one, Python is embedded in the venv. So your system python doesnt really matter. As long as it creates a valid python venv and embeds a valid version of Python, you're fine after sourcing the venv. I believe every other one of those versions libraries, but not the go/cargo/rustc/node programs themselves. There are solutions for each language independently, just as there is for python, but we don't have it as easy as you do with venvs which take care of both at the sane time! But I do agree. If you're using something all the time, just brew install it, which is also what you've done with python I'm assuming. This just brings the power of venvs to every language. Also I'm not surprised that the owner of brew chose to override such a monumentally important command like `env`... Smh