Also using pyenv myself, on platforms where either, or both, new and old version of Python are not available (so on Ubuntu I'm sticking with Anthony Sottile's deadsnakes.)

But I'm not using it to manage virtual envs. For my own development projects, I'm using VirtualFish since I've switched to Fish as my main shell, but I was happy with VirtualenvWrapper when I was still using bash or zsh. I can't live without VirtualFish's autoactivation plugin (which activate a given virtualenv each time you enter your project). There was something similar for Zsh though I don't remember which. Sometimes I forget that I'm not in the right folder, or that I didn't create the virtualenv, or that I removed it in the case of an old project, and I end up polluting my default Python install after a 'pip install ...'. No big deal but always a bit unpleasant.

And as I wrote before, I'm now using pipx to install the apps that I use.

This works not so bad (except for some quirks now and then) but it took quite some time to select the right (for me) tools, to set up the proper config files on my computer, and it can be annoying when working on a server which has not been set up the same way. It also takes some time to explain to collaborators, especially interns or juniors.

So obviously there is room for improvement, especially in terms of simplicity for beginners.

  S.