Re: Python 3 virtualenvs

2015-11-30 Thread Laura Creighton
In a message of Mon, 30 Nov 2015 10:28:46 -0700, Carl Meyer writes: >So I agree that for now you should be sticking with virtualenv (I use it >too), but I hope you'll take another look at venv a few years down the >road, if you find yourself in a situation where all the interpreters you >need are

Re: Python 3 virtualenvs

2015-11-30 Thread Jon Ribbens
On 2015-11-30, Carl Meyer wrote: > (Or maybe virtualenv will make the transition sooner, and you'll start > using venv under the hood for 3.3+ without even realizing it.) It does sound like that would be the ideal solution, and presumably can't be very hard if venv is supposed to do exactly what

Re: Python 3 virtualenvs

2015-11-30 Thread Carl Meyer
On 11/30/2015 10:20 AM, Laura Creighton wrote: > In a message of Mon, 30 Nov 2015 09:32:27 -0700, Carl Meyer writes: >>> I think it is only meant to be used by people who want to install >>> packages but not site-wide, but I am not sure about that. >> >> I don't know what you mean by this either. I

Re: Python 3 virtualenvs

2015-11-30 Thread Laura Creighton
In a message of Mon, 30 Nov 2015 09:32:27 -0700, Carl Meyer writes: >Hi Laura, >I don't know what you mean by this. Venv is intended to do _exactly_ >what virtualenv does, only better. Unless by "what virtualenv does" you >mean "also support Python 2." That is exactly what I mean. >> I think it

Re: Python 3 virtualenvs

2015-11-30 Thread Carl Meyer
Hi Laura, On 11/29/2015 07:12 AM, Laura Creighton wrote: > pyenv is going away. python -m venv is the preferred way to get a venv > > https://bugs.python.org/issue25154 > > Of course if you try it, you may get: > > Error: Command '['/bin/python3.4', '-Im', 'ensurepip', > '--upgrade', '--def

Re: Python 3 virtualenvs

2015-11-29 Thread Laura Creighton
In a message of Sun, 29 Nov 2015 13:23:19 +, Jon Ribbens writes: >I don't know if, in future, pyvenv will be the way to go and >virtualenv will be deprecated, but either way we do not appear >to be there yet. pyenv is going away. python -m venv is the preferred way to get a venv https://bugs

Re: Python 3 virtualenvs

2015-11-29 Thread Jon Ribbens
On 2015-11-29, Laura Creighton wrote: > In a message of Sun, 29 Nov 2015 13:19:46 +0100, Lele Gaifax writes: >>Jon Ribbens writes: > No, Pyvenv is precisely what Daniele can not use. > The problem is that venv does not come with a big sign saying > > ONLY FOR PYTHON 3.x > ABSOLUTELY DOES NOT WORK

Re: Python 3 virtualenvs

2015-11-29 Thread Laura Creighton
In a message of Sun, 29 Nov 2015 13:19:46 +0100, Lele Gaifax writes: >Jon Ribbens writes: > >> On 2015-11-28, D.M. Procida >> wrote: >>> >>> Is something else required? >> >> Debian's package management is mysterious and apparently bizarre >> and frankly in respect to Python, not very good. > >I

Re: Python 3 virtualenvs

2015-11-29 Thread Lele Gaifax
Jon Ribbens writes: > On 2015-11-28, D.M. Procida > wrote: >> >> Is something else required? > > Debian's package management is mysterious and apparently bizarre > and frankly in respect to Python, not very good. I do not agree with you on the quality of Python support on Debian systems, but I

Re: Python 3 virtualenvs

2015-11-28 Thread Jon Ribbens
On 2015-11-28, D.M. Procida wrote: > Jon Ribbens wrote: > >> On 2015-11-28, D.M. Procida > wrote: >> > I have a new installation of Debian Jessie, with Python 2.7 and 3.4 >> > installed. >> > >> > I want to use Python 3.4 by default for most things, so I want >> > virtualenv to create Python 3.

Re: Python 3 virtualenvs

2015-11-28 Thread D.M. Procida
Jon Ribbens wrote: > On 2015-11-28, D.M. Procida wrote: > > I have a new installation of Debian Jessie, with Python 2.7 and 3.4 > > installed. > > > > I want to use Python 3.4 by default for most things, so I want > > virtualenv to create Python 3.4 virtualenvs unless I ask it to > > otherwise.

Re: Python 3 virtualenvs

2015-11-28 Thread Jon Ribbens
On 2015-11-28, D.M. Procida wrote: > I have a new installation of Debian Jessie, with Python 2.7 and 3.4 > installed. > > I want to use Python 3.4 by default for most things, so I want > virtualenv to create Python 3.4 virtualenvs unless I ask it to > otherwise. > > It turns out that this seems t

Re: Python 3 virtualenvs

2015-11-27 Thread D.M. Procida
Laura Creighton wrote: > In a message of Sat, 28 Nov 2015 00:37:21 +, D.M. Procida writes: > >I have a new installation of Debian Jessie, with Python 2.7 and 3.4 > >installed. > > > >I want to use Python 3.4 by default for most things, so I want > >virtualenv to create Python 3.4 virtualenvs

Re: Python 3 virtualenvs

2015-11-27 Thread Laura Creighton
In a message of Sat, 28 Nov 2015 00:37:21 +, D.M. Procida writes: >I have a new installation of Debian Jessie, with Python 2.7 and 3.4 >installed. > >I want to use Python 3.4 by default for most things, so I want >virtualenv to create Python 3.4 virtualenvs unless I ask it to >otherwise. > >It