For example, with virtualenv you can choose to use a mix of globally- and locally-installed packages. With venv you can't. (You get global or local, but not both.)
The database driver and scipy are installed globally. Everything else is local to the environment.
Not hell at all, especially compared to compiling numpy/scipy every time you want to spin up a venv that uses a single feature.
Examples other than DB drivers and scipy exist. Compiling software isn't really that hard, but it's an unnecessary hurdle in many cases - especially when you've already bought into an OS that does binary distributions specifically so you don't have to compile anything.
I'd be comfortable agreeing that any pure-python package should be venv only, but not that every package should be.
> From here on out, now the world is your oyster; you can pip install to your heart’s content, and you probably won’t even need to compile any C for most packages. These instructions don’t depend on Python version, either: as long as it’s up-to-date, the same steps work on Python 2, Python 3,
Nit: I suppose installing virtualenv works in 2 and 3, but hasn't venv in 3 made that unnecessary?