IMHO venvs are fine as an implementation detail, a building block for a slicker tool. The annoyance with venvs is you have to create and activate them. In cont

IMHO venvs are fine as an implementation detail, a building block for a slicker tool. The annoyance with venvs is you have to create and activate them. In contrast for cargo (or stack or dotnet or yarn or pipenv or poetry), you just run the build tool in the project directory. Another limitation of venv is it doesn't solve the problem of pinning a versions of Python, so you need another tool.