On 01/08/2014 10:06 AM, Kristján Valur Jónsson wrote:
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 think it's much better than blocking polyglot code altogether. Some
kludging is to be expected when writing polyglot code. Polyglot
libraries like 'six' or the 'future' module could make this available by
default.
> 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
You'd tie your own plans to what the cPython developers are willing to
add to the __future__ modules in Python 3.4? Why create this
coordination burden when you can easily avoid it?
Regards,
Martijn
_______________________________________________
Stackless mailing list
[email protected]
http://www.stackless.com/mailman/listinfo/stackless
