Martin v. Loewis wrote:
> Greg Ewing <greg@cosc.canterbury.ac.nz> writes:
>
>
>>Am I right in thinking that a problem can only
>>occur if a tasklet switch occurs between the time
>>the local variable is created and the time it's
>>used? If the same tasklet is running both times,
>>the stack should be back in it's right place.
>
>
> Not necessarily. Christian segments the stack into slices, and only
> keeps the top-of-stack slice on the stack. So even within a single
> tasklet, you cannot refer to stack variables of your callers, if those
> callers are far away.
Right! At the moment it appears to be the only problem.
It isn't the tasklet switching (that behaves as Greg suspects),
but the slicing code.
By setting the slicing recursion interval to above 20,
the Tcl stuff works.
Maybe I'm just fine by patching _tkinter a little bit,
so that it influences stack slicing in a healthy way?
cheers - chris
--
Christian Tismer :^) <mailto:tismer@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 pager +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/
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4