[PEAK] Task containment and isolation

Niki Spahiev niki.spahiev at gmail.com
Sat Jul 28 06:36:37 EDT 2007

2007/7/27, Phillip J. Eby <pje at telecommunity.com>:
> At 04:51 PM 7/26/2007 -0400, Phillip J. Eby wrote:
> >* ``task``, ``Pause``, ``Return``, ``resume()``, and ``TaskCell``
> >   (support for pseudothreads similar to ``peak.events.Task``)
> >...
> >* Remove dependency on the unreleased "Contextual" package
> >   (we're currently only using one exception class from there, and
> >   the features that will require it in future will be in either the
> >   "TrellisIO" or "TrellisDB" packages; more details below)
> It looks like this isn't quite as easy as I thought.  There's a
> conflict, in that if I support pseudothreads, I need a way to let
> them have different "Contextual" contexts, and prevent pollution
> between different contexts.  Otherwise, there's no way to create
> fully isolated pseudo-threads with their own database connections,
> transactions, etc.

How does this relate with stackless python and greenlets?

Niki Spahiev

More information about the PEAK mailing list