tismer at tismer.com
Mon Nov 10 20:32:52 CET 2003
Giovanni Bajo wrote:
> On Sunday, November 09, 2003 4:13 PM [GMT+1=CET],
> Christian Tismer <tismer at tismer.com> wrote:
>>One problem is to avoid as much C stack situations as
>>possible, since I see no healthy way to unpickle a C stack.
> In my experience, the biggest problem we found out with thread pickling is that
> we were unable to pickle threads due to "CFrame" objects. As Christian explained
> us, these are not C stacks (which we *never* create, and it's not even hard in
> our application), but a different kind of object, which is created in very
> common situations, like tasklet(self.method)(). It was way to common in our
The CFrame objects are just an omission at the moment.
They will be picklable as soon as I get at it.
(Actually after finishing the damned tasklet destruction :-)
> Another issue is that it _looked_ like a tasklet switching was happening in the
> middle of object unpickling (causing of course misbehaviour of the program). We
> were not sure it was actually our fault (like a stackless.schedule() during
> __setstate__ or something), but the issue ended up being too complex to debug.
I will add some thorough testing code for these issues.
Just a matter of time (and can be accelerated if I get a
small contract for this).
ciao - chris
Christian Tismer :^) <mailto:tismer at tismer.com>
Mission Impossible 5oftware : Have a break! Take a ride on Python's
Johannes-Niemeyer-Weg 9a : *Starship* http://starship.python.net/
14109 Berlin : PGP key -> http://wwwkeys.pgp.net/
work +49 30 89 09 53 34 home +49 30 802 86 56 mobile +49 173 24 18 776
PGP 0x57F3BF04 9064 F4E1 D754 C2FF 1619 305B C09C 5A3B 57F3 BF04
whom do you want to sponsor today? http://www.stackless.com/
Stackless mailing list
Stackless at www.tismer.com
More information about the Stackless