I'm currently studying all I can find on stackless python, PYPY and the concepts they've brought to Python, and so far I wonder : since stackless python claims to be 100% compatible with CPython's extensions, faster, and brings lots of fun stuffs (tasklets, coroutines and no C stack), how comes it hasn't been merged back, to become the standard 'fast' python implementation ?

There is a long history to it, and multiple reasons influenced that status. In summary, some of the reasons were: - Stackless Python was never officially proposed for inclusion into Python (it may be that parts of it were, and of those parts actually did get added). - Stackless Python originally was fairly unmaintainable; this prevented its inclusion. - in its current form, it has limited portability, as it needs to be ported to each microprocessor and operating system separately. CPython has so far avoided using assembler code, and is fairly portable. Regards, Martin

Hello,

I'm currently studying all I can find on stackless python, PYPY and the concepts they've brought to Python, and so far I wonder : since stackless python claims to be 100% compatible with CPython's extensions, faster, and brings lots of fun stuffs (tasklets, coroutines and no C stack), how comes it hasn't been merged back, to become the standard 'fast' python implementation ?

I'm not sure Stackless ever claimed to be faster than CPython for standard tasks (i.e., not coroutine-related). Do you have any pointers to this? As for coroutines, the greenlets (*) package is said to bring them to the standard interpreter. (*) http://codespeak.net/py/dist/greenlet.html Regards Antoine.