Corey Seliger <co...@seligerfamily.org> 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
New submission from Corey Seliger <co...@seligerfamily.org>:
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-
