Sidebar: /usr/bin/python seems to be the implicit default too, even for
this Python3-based version.
Thanks for staying with me in such a calm manner, Barry. I can get on
board with that but I'm still seeing real-world problems with the
outcome. It's probably something unrelated to Python 3. When it comes to
pip+source packages that have to be built it can't do it. I don't know
why. You can repro on a fresh computer:
sudo apt install virtualenv python-virtualenv python-dev mercurial
/usr/bin/virtualenv -p /usr/bin/python2.7 test-venv
./test-venv/bin/pip install
hg+https://bitbucket.org/bittner/django-apptemplates/#egg=django-apptemplates
You'll see a hairy error about "ImportError: No module named
_markerlib". Activating doesn't make any difference. I've had this
problem with quite a few packages now.
If you install python-pip and then run `sudo pip install virtualenv`,
and use /usr/local/bin/virtualenv to create the environment, you can
install everything. The versions of pip used appear to be the same. I'm
honestly unsure what's causing this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1550923
Title:
16.04's virtualenv uses Python 3 but python executable is Python 2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-virtualenv/+bug/1550923/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
