On Feb 29, 2016, at 06:56 PM, Oli wrote: >And that's the problem. I don't disagree with a want to move away from >Python 2, but there are many developers and organisations that are still >managing their upgrades from 2-to-3, who maintain multiple environments >with both versions. I have dozens of virtualenvs on my server.
If you only care about the version of Python deployed in the virtualenv, and not how the /usr/bin/virtualenv script actually gets invoked (which is likely what you're asking), then this works fine: $ virtualenv -p python /tmp/p2 Explicit is better than implicit. -- 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
