R. David Murray added the comment:
This is a feature that actually supports your use case, as well as the use
cases of those who *don't* want to strap the python version: you get what you
ask for. If you call venv with 'python3', you get a venv that will use your
new python if you upgrade yo
Corey Seliger added the comment:
Here is the write-up I posted over on the pyenv issues page:
This is apparently a behavior issue in the way venv works. Not only does this
impact 3.6.x, I also confirmed that the same issue occurs with venv in general
using the stock 3.5 Python that comes with
New submission from Corey Seliger :
The venv module does not evenly create the necessary binaries/symlinks when
building virtualenvs. If you call venv like this:
seliger@core:~/venvs$ python3 -m venv venvA
seliger@core:~/venvs$ ls -l venvA/bin/
total 32
-rw-r--r-- 1 seliger seliger 2143 Dec 28