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,
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
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,
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
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.
>> >
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
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
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
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?
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
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
>
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
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
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
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
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
16 matches
Mail list logo