[Stackless] __future__ policy
Martijn Faassen
faassen at startifact.com
Tue Jan 7 13:44:16 CET 2014
Hi there,
I understand Stackless 2.8 is considering the following:
from __future__ import nonlocal
It was pointed out on the #python2.8 channel yesterday that this leads
to a problem when upgrading Stackless 2.8 code to Python 3.x code, as
from __future__ import nonlocal
is an error there. So it becomes impossible to write code that runs both
on Stackless 2.8 and Python 3.3, for instance.
It was suggested you introduce another magic module specific for
Stackless, say:
from __stackless__ import nonlocal
and then you can write a simple dummy module __stackless__ in Python 3.3
that does absolutely nothing. That way it becomes possible to write
polyglotted code between Stackless and Python 3.3.
Regards,
Martijn
More information about the Stackless
mailing list