Hi,
On 07/01/14 17:52, Martijn Faassen wrote:
On 01/07/2014 04:25 PM, Martijn Faassen wrote:
Is it a goal of Stackless 2.8 to help making it easier to port code
written for it to Python 3.x?
If so, would you consider adding backported str/bytes facilities like in
the 'future' module, as described in python-future.org? I haven't dug
into its code yet so I may be wrong, but I speculated here how it works:
https://groups.google.com/d/msg/comp.lang.python/CvtQVzZWcUE/bvt3Cg0FhSoJ
After further analysis it turns out it doesn't quite work that way.
Instead I it works like I described here on this issue:
https://github.com/PythonCharmers/python-future/issues/27
I think it'd be interesting to support behavior like this in Stackless
2.8, as it would I think be of genuine benefit to smoothen the upgrade
path to Python 3.x code.
If I understand it correctly, a consequent support for str/bytes would
need to make str and bytes explicitly incompatible.
But that is a huuuge change, and too much work.
It would mean to implement everything that python3 changed there.
I think we should not artificially enforce str/bytes incompatibility.
Code can be checked by running it on a python 3 interpreter, that should
be good enough.
cheers - chris
--
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
