Oh if it were that easy. `python -m virtualenv` does not work. Python2's virtualenv couldn't be called as a module.
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. Changing how a basic tool like virtulenv is packaged (indeed, in practice it ISN'T packaged for Python 2 now) just annoying. The easiest fix is `sudo pip install virtualenv` which supplants the whole thing and means you have to use the full path for the Python3 version. If you still haven't seen how silly the state of this is, just look at pip (python-pip, /usr/bin/pip). It's still Python 2!! So no. You could break all the things, break all the people, or put things back to how they should be. A wontfix here really only serves to make Ubuntu (and Debian) worse. -- 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
