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]. _______________________________________________ Stackless mailing list [email protected] http://www.stackless.com/mailman/listinfo/stackless
