[Stackless] nonlocal for 2.8

Richard Tew richard.m.tew at gmail.com
Mon Dec 23 20:54:13 CET 2013


Yes, give deprecation warnings and require the import seems like a
prudent approach for backwards compatibility breaking approaches.

Cheers,
Richard.

On 12/24/13, Christian Tismer <tismer at stackless.com> wrote:
> Then let's be consequent and add it via another future:
>
> from __future__ import nonlocal
>
> cheers - chris
>
> On 23/12/13 09:44, Kristján Valur Jónsson wrote:
>> The only issue I can see (apart from work) is potential name clashes with
>> a new keyword. I wonder how serious an issue that might be?
>>
>> ________________________________________
>> From: stackless-bounces at stackless.com [stackless-bounces at stackless.com] on
>> behalf of Richard Tew [richard.m.tew at gmail.com]
>> Sent: Sunday, December 22, 2013 11:57 PM
>> To: stackless at stackless.com
>> Subject: [Stackless] nonlocal for 2.8
>>
>> Hi,
>>
>> I haven't looked into what's involved yet, but how do we feel about
>> backporting nonlocal to 2.8?
>>
>> Cheers,
>> Richard.
>>
>> _______________________________________________
>> Stackless mailing list
>> Stackless at stackless.com
>> http://www.stackless.com/mailman/listinfo/stackless
>>
>> _______________________________________________
>> Stackless mailing list
>> Stackless at stackless.com
>> http://www.stackless.com/mailman/listinfo/stackless
>
>
> --
> Christian Tismer             :^)   <mailto:tismer at stackless.com>
> Software Consulting          :     Have a break! Take a ride on Python's
> Karl-Liebknecht-Str. 121     :    *Starship* http://starship.python.net/
> 14482 Potsdam                :     PGP key -> http://pgp.uni-mainz.de
> phone +49 173 24 18 776  fax +49 (30) 700143-0023
> PGP 0x57F3BF04       9064 F4E1 D754 C2FF 1619  305B C09C 5A3B 57F3 BF04
>        whom do you want to sponsor today?   http://www.stackless.com/
>
>
> _______________________________________________
> Stackless mailing list
> Stackless at stackless.com
> http://www.stackless.com/mailman/listinfo/stackless
>



More information about the Stackless mailing list