> 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
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
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
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
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,
On Feb 28, 2016, at 01:29 PM, Oli wrote:
> - Python 2 is still the default?
It depends on your definition of "default". If you mean, which Python does
/usr/bin/python invoke, then yes, 2.7 is the default and likely will be for a
long time in Debian/Ubuntu. We have no plans to change the
