On 2/21/10 7:32 PM, Richard Tew wrote:
My Google Alert picked up an interesting reference to Stackless this
morning. It relates to how if the Unladen Swallow merge into Python
goes ahead, how Stackless might need to change (with us doing the
work).
http://www.python.org/dev/peps/pep-3146/#known-incompatibilities
-- >8 -- 8< --
Invasive forks of CPython such as Stackless Python [115] are more
challenging to support. Since Stackless is highly unlikely to be
merged into CPython [116] and an increased maintenance burden is part
and parcel of any fork, we consider compatibility with Stackless to be
relatively low-priority. JIT-compiled stack frames use the C stack, so
Stackless should be able to treat them the same as it treats calls
through extension modules. If that turns out to be unacceptable,
Stackless could either remove the JIT compiler or improve JIT code
generation to better support heap-based stack frames [117], [118].
I am still at designing Stackless Lite. That should work with Unladen.
Although I think there will not be much porting effort necessary.
Besides that, Stackless is going Psyco, which got higher priority
meanwhile. More on that next week, when I have official infos.
Under that new move, X86 users will most probably stick with the
Psyco Jit.
cheers - chris
--
Christian Tismer :^)<mailto:[email protected]>
tismerysoft GmbH : Have a break! Take a ride on Python's
Johannes-Niemeyer-Weg 9A : *Starship* http://starship.python.net/
14109 Berlin : PGP key -> http://wwwkeys.pgp.net/
work +49 30 802 86 56 mobile +49 173 24 18 776 fax +49 30 80 90 57 05
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
