[Stackless] You cannot __reduce__ the tasklet ...
tismer at stackless.com
Wed Jun 2 19:47:50 CEST 2004
Arman Bostani wrote:
> Another dumb question: why do you want to forbid execution of pickled
> "current" tasklets? What's special about them?
It is that I cannot capture the current frame in a consistent
way, since it is in a call to the tasklet's __reduce__ which
is not stackless. So the current tasklet would always show
up as one that raises an exception when run.
But maybe this would be ok.
This is where I wasn't sure about, but I agree that forbidding
it is a half-assed solution. The idea of tasklet pickling
is to pickle everything, even if it cannot be revived, just
to have some state to inspect or partially execute.
I will change this when i get an idea what to do.
cheers - chris
Christian Tismer :^) <mailto:tismer at stackless.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 stackless.com
More information about the Stackless