On Thu, Nov 10, 2016 at 12:02 AM, Thomas Goirand wrote: > The point is, some people also use venvs. In a world of Python 3 only, > some upstream will continue to use /usr/bin/python (IMO, rightly). We > should be able to provide a default implementation for these scripts.
I think this is a bug in virtualenv: $ virtualenv -p /usr/bin/python3 test Already using interpreter /usr/bin/python3 Using base prefix '/usr' New python executable in /home/pabs/test/bin/python3 Also creating executable in /home/pabs/test/bin/python Installing setuptools, pkg_resources, pip, wheel...done. $ virtualenv -p python3 test Already using interpreter /usr/bin/python3 Using base prefix '/usr' New python executable in /home/pabs/test/bin/python3 Also creating executable in /home/pabs/test/bin/python Installing setuptools, pkg_resources, pip, wheel...done. -- bye, pabs https://wiki.debian.org/PaulWise
