> -----Original Message----- > From: [email protected] [mailto:stackless- > [email protected]] On Behalf Of Kristján Valur Jónsson > Sent: 8. janúar 2014 08:56 > To: The Stackless Python Mailing List > Subject: Re: [Stackless] __future__ policy > "from __stackless__ import nonlocal" > > does not help one part of what we are trying to achieve, allow polyglot code > between 2.x and 3 to use nonlocal. > Because for the module that uses this code to work, you'd have to have to > run it in either stackless 2.8 or a new version of stackless 3.4 or whatever. > i.e. > you'd be tying your code to stackless, even if It were not doing any stackless > related stuff.
Ok, I see now that you could also be providing a __stackless__.py module to deal with the default 3.x case. Still, a very cludgy proposition. I wonder how cPython would view adding no-op codes to the 3.4 __future__ module at this stage? What would we like to propose? nonlocal and yield_from are the obvious candidates K _______________________________________________ Stackless mailing list [email protected] http://www.stackless.com/mailman/listinfo/stackless
