Re: python-pip and python-virtualenv broken in sid after upgrade to python 2.7.7rc1
On Tuesday 03 June 2014 20:11:21 Barry Warsaw wrote: > Then requests and all other dependents > (including those that use the .whls) should get it. I plan to update requests next week, unfortunately I can't work on it during this weekend. If needed, Barry, please go with a team upload! ;) Thanks! -- Daniele Tricoli 'Eriol' http://mornie.org signature.asc Description: This is a digitally signed message part.
Re: Proposed changes to python-virtualenv
Hi Barry (2014.06.02_22:51:24_+0200) > >Sounds reasonable to me, the only “downside” is that virutalenv will default > >to Python 3, which is probably not what most people want (however they > >can do virtualenv -p python2). > > But it's what most people *should* want . Won't python 3 users be using python3 -m venv? The only real advantage of virtualenv over venv is bundled pip, but stdlib python has that too, now... SR -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 461 1230 C: +27 72 419 8559 -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140604202031.gc3...@bach.rivera.co.za
Re: Proposed changes to python-virtualenv
On Jun 4, 2014, at 4:20 PM, Stefano Rivera wrote: > Hi Barry (2014.06.02_22:51:24_+0200) >>> Sounds reasonable to me, the only “downside” is that virutalenv will default >>> to Python 3, which is probably not what most people want (however they >>> can do virtualenv -p python2). >> >> But it's what most people *should* want . > > Won't python 3 users be using python3 -m venv? > > The only real advantage of virtualenv over venv is bundled pip, but > stdlib python has that too, now… Maybe, virtualenv has other advantages, some of which are additional tooling written around it (virtualenvwrapper etc). It also has the benefit that it works across multiple versions of Python, so if someone wants to create Python 2 and Python <3.4 virtual environments, they are likely to be using virtualenv for consistency sake. - Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA signature.asc Description: Message signed with OpenPGP using GPGMail
Re: Proposed changes to python-virtualenv
On Mon, Jun 2, 2014 at 10:51 PM, Barry Warsaw wrote: > On Jun 02, 2014, at 04:43 PM, Donald Stufft wrote: > > >Sounds reasonable to me, the only “downside” is that virutalenv will > default > >to Python 3, which is probably not what most people want (however they > >can do virtualenv -p python2). > > Barry, would it be sensible to default to python2 (so keep existing outside behaviour unchanged) and then only after a grace period and enough announcements make python3 the default? To me doing it right now seems like breaking lots of scripting for no good reason. Thanks ZK > But it's what most people *should* want . > > Seriously though, I wonder if this is a problem or if some transition or > wider > announcement needs to be made. > > -Barry >
Re: Proposed changes to python-virtualenv
On Jun 04, 2014, at 10:20 PM, Stefano Rivera wrote: >Won't python 3 users be using python3 -m venv? Or `pyvenv-3` once I get that working. ;) -Barry -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140604173842.05773...@anarchist.wooz.org
Re: Proposed changes to python-virtualenv
On Jun 04, 2014, at 11:07 PM, Zygmunt Krynicki wrote: >Barry, would it be sensible to default to python2 (so keep existing outside >behaviour unchanged) and then only after a grace period and enough >announcements make python3 the default? To me doing it right now seems like >breaking lots of scripting for no good reason. Possibly, but if we're going to make the change, it makes sense to me to do it in Jessie. So what would be a good grace period? Looking a little more at the implementation of virtualenv, I think it might be possible to give the -p/--python option a default of `python2` to mimic the old behavior. The difference is that virtualenv re-execs itself with the specified interpreter when it is not sys.executable. So after the port to Python 3, the default would re-exec itself with /usr/bin/python2. That doesn't seem terrible to me. (A possible downside is if Python 2 isn't installed, in which case you'd get an error. That's probably unlikely to happen in practice.) Still, it begs the question: when would we switch the default back to python3? -Barry signature.asc Description: PGP signature
