Not OP but anecdotally, this is how my workflow looks like: 1. Install pyenv to a central location of my choice, e. g. ~/.pyenv (this helps manage all those di

Not OP but anecdotally, this is how my workflow looks like: 1. Install pyenv to a central location of my choice, e. g. ~/.pyenv (this helps manage all those different Python versions piling up from all the isolated projects I have.) 2. Install pipenv as a stand-alone tool. Doesn’t matter which Python I’m using, I just want to have it in my PATH. 3. Now I’m ready to create fully isolated projects using pipenv. Not only does pipenv create a venv right inside my project directory for me, it also helps me manage and lock dependencies. It also talks to pyenv so it can fetch the per-project Python version for me; this is especially useful when collaborating with others on the same project; they can reliably check out the project without having to manage specific Python versions themselves. YMMV but I’ve had a stable experience using this setup so far.