[Stackless] Sprinting at PyCon

Alain Poirier alain.poirier at net-ng.com
Sun Apr 13 18:07:37 CEST 2014

Hi all,

I would like to discuss how it'd be possible or not for Stackless to follow the
same path than PyPy:

  - A simpler Stackless core, with only the 'tealet' / '_continuation' stack
    switch, writing in C. Exposing the same API than PyPy.
    IIRC, Krisjan already has such a Stackless version.

  - All the high level features of Stackless like Tasklets and Channels moved to
    the 'stackless.py' pure Python module.

  - An emulation of the greenlets API, in a 'greenlet.py' pure Python module.

  - Bonus point if these 'stackless.py' and 'greenlet.py’ modeules are shared /
    co-developed with the PyPy project :)

I see several advantages then:

  - Greenlets and Stackless features being Python modules, easier experimentations
    are possible. For example writing other scheduling policy or higher concurrency
    primitives such like Andrew's select/join.

  - With a 'greenlet.py' compatible module, lots of softwares like ‘gevent’ could
    work without any modification.

  - Works on 'greenlet.py' and 'stackless.py' can profit both to Python Stackless
    and PyPy.

Just my 2 cents,

More information about the Stackless mailing list