[Stackless] Tasklet Slot Inheritance

Kristján Valur Jónsson kristjan at ccpgames.com
Thu May 10 16:01:01 CEST 2007


This could be a flextype bug.

> -----Original Message-----
> From: stackless-bounces at stackless.com [mailto:stackless-
> bounces at stackless.com] On Behalf Of Richard Tew
> Sent: Thursday, May 10, 2007 07:49
> To: Edward Faulkner
> Cc: stackless at stackless.com
> Subject: Re: [Stackless] Tasklet Slot Inheritance
>
> On 5/9/07, Edward Faulkner <ef at alum.mit.edu> wrote:
> > I've noticed a weird behavior when I inherit from tasklet.  If my
> > class doesn't define __slots__, I can define and use extra member
> > variables as expected, and they remain valid for the life of the
> > object.
> >
> > But if I define __slots__ to limit the possible member variables,
> they
> > get deleted when the tasklet exits, even though I still have a
> > reference to it.
>
> Thanks for the report.  I'll add it to the list of things to look
> into.  If anyone else wants to take a shot at looking into it before I
> get around to it, please feel free.  It should be relatively
> straightforward.
>
> Cheers,
> Richard.
>
> _______________________________________________
> Stackless mailing list
> Stackless at stackless.com
> http://www.stackless.com/mailman/listinfo/stackless

_______________________________________________
Stackless mailing list
Stackless at stackless.com
http://www.stackless.com/mailman/listinfo/stackless



More information about the Stackless mailing list