On Feb 29, 2016, at 11:39 PM, Oli wrote: >Sidebar: /usr/bin/python seems to be the implicit default too, even for >this Python3-based version.
I'm not quite sure what that means. >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. Yep, we're going through a bit of a transition with the stack of tools in Xenial. I think we're quite close to full resolution, but the above is a known (and now fixed!) problem. There may be a little more churn as we work out some more details, but don't worry, it'll all work by the time 16.04 is out. -- 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
