I don't think so. Stackless.getcurrent() is still available to be called. also, I don't see why the error_handler ought to be unique to a thread, any more than __taskelet__ and __channel__ are. However, if we desire a more fine-grained control, then I thihk subclassing the tasklet would be the right way to do this. K
> -----Original Message----- > From: Richard Tew [mailto:[email protected]] > Sent: 8. apríl 2013 21:02 > To: Kristján Valur Jónsson > Cc: The Stackless Python Mailing List > Subject: Re: [Stackless] added tasklet.throw > > Is there any value in passing in the tasklet the exception happened in, as the > first argument of the error handler? > If every thread has a scheduler, should the error handler be stored in the > thread context? > > On Tue, Apr 9, 2013 at 6:02 AM, Kristján Valur Jónsson > <[email protected]> wrote: > > Done, check it out in the repo. > > > > > > _______________________________________________ Stackless mailing list [email protected] http://www.stackless.com/mailman/listinfo/stackless
