> Re: Changing how a basic tool like virtulenv is packaged ... is just annoying
I realize this bug is over a year old now, but I am just now arriving here. I've been encountering it here and there for several months. It was just luck that I noticed a default='python2' line in the apt virtualenv.py, and thought it a bit odd for a python3 package. That oddness allowed me to fumble the correct search terms to find this (try googling "python 3 makes a python 2 virtual environment"). In addition to causing me to question my own sanity, it has been causing a great deal of confusion on my team (we've only recently started upgrading servers and workstations from 14LTS to 16LTS - we only run the LTS versions). I can appreciate that there is some complexity involved in migrating an entire operating system to a new python version. However, when I say `python3 -m virtualenv`, I expect a python3 virtual environment to be produced. But, on Xenial (and nowhere else), I always get a python2 environment. The reason we use virtual environments is to keep from bumping into the python needs of the OS. It seems to me that it would be beneficial to update any code in Ubuntu which expects a python2 environment to use -p parameter, rather than requiring *all* python3 code using virtual environments to know about this change and update for it. Consider this a vote to restore the original behavior :) -- 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
