Re: [Python-Dev] Proposing the deprecation of the pyvenv script

2015-09-19 Thread Paul Moore
On 19 September 2015 at 19:37, Brett Cannon wrote: > Guys, this thread is about removing the pyvenv script, not pip. If you want > to start a discussion about pip and its command structure that should > probably happen on pip's issue tracker or over at distutils-sig. Sorry,

Re: [Python-Dev] Proposing the deprecation of the pyvenv script

2015-09-19 Thread Brett Cannon
Guys, this thread is about removing the pyvenv script, not pip. If you want to start a discussion about pip and its command structure that should probably happen on pip's issue tracker or over at distutils-sig. On Sat, 19 Sep 2015 at 10:37 Sven R. Kunze wrote: > On 19.09.2015

Re: [Python-Dev] Proposing the deprecation of the pyvenv script

2015-09-19 Thread Stephen J. Turnbull
Terry Reedy writes: > Am I correct in guessing that on Windows, at least, R and Emacs do *not* > run in Command Prompt? I'm not sure what you mean by that. Of course they do run under Command Prompt, but the limitations of the command window are so severe that almost nobody ever does that,

Re: [Python-Dev] Proposing the deprecation of the pyvenv script

2015-09-19 Thread Sven R. Kunze
On 19.09.2015 07:24, Stephen J. Turnbull wrote: Barry Warsaw writes: > One thing that came up in a similar discussion is pip, and the > suggested move to `python -m pip`, which makes a lot of sense. > However, *inside* a virtualenv, there's no ambiguity about the > Python version

Re: [Python-Dev] Proposing the deprecation of the pyvenv script

2015-09-19 Thread Paul Moore
On 19 September 2015 at 06:49, Terry Reedy wrote: > On 9/19/2015 1:24 AM, Stephen J. Turnbull wrote: >> >> Barry Warsaw writes: >> >> > One thing that came up in a similar discussion is pip, and the >> > suggested move to `python -m pip`, which makes a lot of sense. >> >

Re: [Python-Dev] Proposing the deprecation of the pyvenv script

2015-09-19 Thread Paul Moore
On 19 September 2015 at 10:12, Sven R. Kunze wrote: > The only question I have: is there a particular reason (not technical one) > why there are many pips on my PC? That's not an unreasonable question, but (IMO) most of the answers are technical, or amount to "why would you

Re: [Python-Dev] Proposing the deprecation of the pyvenv script

2015-09-19 Thread Sven R. Kunze
On 19.09.2015 14:44, Paul Moore wrote: On 19 September 2015 at 10:12, Sven R. Kunze wrote: The only question I have: is there a particular reason (not technical one) why there are many pips on my PC? That's not an unreasonable question, but (IMO) most of the answers are

Re: [Python-Dev] Proposing the deprecation of the pyvenv script

2015-09-19 Thread Paul Moore
On 19 September 2015 at 18:15, Sven R. Kunze wrote: >> So, to directly answer: >> >> Because there are technical challenges that no-one has stepped up to >> solve. > > > Let's solve them. :) I thought my point was "yes, go for it - your code contribution would be

Re: [Python-Dev] Proposing the deprecation of the pyvenv script

2015-09-19 Thread Sven R. Kunze
On 19.09.2015 19:19, Paul Moore wrote: I thought my point was "yes, go for it - your code contribution would be appreciated" :-) Paul Well, before coding shouldn't we have vision and a plan for pip somehow and pinpoint it somewhere where everybody who's willing to contribute can see it?

Re: [Python-Dev] Proposing the deprecation of the pyvenv script

2015-09-18 Thread Nick Coghlan
On 18 September 2015 at 05:04, Barry Warsaw wrote: > On Sep 17, 2015, at 06:40 PM, Brett Cannon wrote: > >>I propose that the pyvenv script be deprecated in Python 3.5.1 and >>removed in Python 3.8. The reason for this proposal is because it is >>non-obvious what version of

Re: [Python-Dev] Proposing the deprecation of the pyvenv script

2015-09-18 Thread Stephen J. Turnbull
Barry Warsaw writes: > One thing that came up in a similar discussion is pip, and the > suggested move to `python -m pip`, which makes a lot of sense. > However, *inside* a virtualenv, there's no ambiguity about the > Python version associated with direct `pip` invocation, so it still >

Re: [Python-Dev] Proposing the deprecation of the pyvenv script

2015-09-18 Thread Nick Coghlan
On 19 September 2015 at 01:16, Barry Warsaw wrote: > On Sep 18, 2015, at 07:53 PM, Nick Coghlan wrote: > >>I currently use pyvenv directly, but I agree with starting a migration >>to only supporting the more explicit "python -m venv". There's always >>an inherent ambiguity on

Re: [Python-Dev] Proposing the deprecation of the pyvenv script

2015-09-18 Thread Terry Reedy
On 9/19/2015 1:24 AM, Stephen J. Turnbull wrote: Barry Warsaw writes: > One thing that came up in a similar discussion is pip, and the > suggested move to `python -m pip`, which makes a lot of sense. > However, *inside* a virtualenv, there's no ambiguity about the > Python version

Re: [Python-Dev] Proposing the deprecation of the pyvenv script

2015-09-18 Thread Barry Warsaw
On Sep 18, 2015, at 07:53 PM, Nick Coghlan wrote: >I currently use pyvenv directly, but I agree with starting a migration >to only supporting the more explicit "python -m venv". There's always >an inherent ambiguity on *nix with unqualified version sensitive >Python commands as to whether they're

[Python-Dev] Proposing the deprecation of the pyvenv script

2015-09-17 Thread Brett Cannon
I opened http://bugs.python.org/issue25154 for this idea and below is what I put in the issue as to why I think we should deprecate the pyvenv script in favour of `python3 -m venv`. I propose that the pyvenv script be deprecated in Python 3.5.1 and removed in Python 3.8. The reason for this

Re: [Python-Dev] Proposing the deprecation of the pyvenv script

2015-09-17 Thread Barry Warsaw
On Sep 17, 2015, at 06:40 PM, Brett Cannon wrote: >I propose that the pyvenv script be deprecated in Python 3.5.1 and >removed in Python 3.8. The reason for this proposal is because it is >non-obvious what version of Python a pyvenv command is tied to (heck, >it isn't necessarily obvious that