Howdy
I see it, too now.
Took me a while.
Yes it makes sense, because when porting a module, you want it to be used
everywhere, and _not_ just on a small subset of all python 3 flavors.
The only thing that I dislike is the name __slpfuture__.
It is a second future module name, right, but it has nothing to do with
stackless,
but just happens to be added to stackless to help out.
Anybody could add such a synonym, it is really a small
patch and nothing to claim as a stackless achievement.
Just a great idea from Kris ;-)
On 08.01.14 15:13, Anselm Kruis wrote:
Good idea. And it even works if you need future modules from CPython
and Stackless:
------8<----------8<----------8<----------8<----------8<---
from __future__ import absolute_import
from __slpfuture__ import print_function
print ("hello World!")
------8<----------8<----------8<----------8<----------8<---
Fortunately more than one from __future__ line is allowed.
Cheers
Anselm
Am 08.01.2014 14:42, schrieb Kristján Valur Jónsson:
I'm getting to see Martijn's point.
So, how about this: We make __slpfuture__ a synonym for __future__
in 2.8.
We add "nonlocal" and "yield_from" arguments.
We then provide a __slpfuture__.py module with those things defined.
If we then manage to convince cpython that they should add no-op
support for our 2.8-slp things, that's great! Otherwise, we can just
stick with using __slpfuture__.
--
Christian Tismer :^) <mailto:[email protected]>
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
[email protected]
http://www.stackless.com/mailman/listinfo/stackless
