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
On Mon, Jun 2, 2014 at 10:51 PM, Barry Warsaw ba...@debian.org 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 wink. 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
