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 scri
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
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).
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
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 us
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
6 matches
Mail list logo
