[Stackless] Stackless status

Just van Rossum just at letterror.com
Mon Oct 9 09:31:38 CEST 2000

At 10:10 PM -0400 08-10-2000, Gordon McMillan wrote:
>What I've found is that an exception
>that crosses a continuation-boundary produces a leak (at
>least, that's my best deduction). If you catch the exception
>within the continuation, all is fine; but if you let it cross back
>into the guy that called the continuation, you're stuck. Seems
>to me I discovered this by toying with generator-like patterns:
>throwing an IndexError in the continuation, so the (caller of
>the) caller would fall out of a for loop. That's with 1.1.

This sounds very similar to what I've posted. (Can _anyone_ reproduce the
leak in my script? Even with Chris' latest version it leaks, but Chris
can't reproduce it.)

I've just tried to reproduce what you describe without the timeslice()
function, and failed. Do you have a minimal example?


Stackless mailing list
Stackless at starship.python.net

More information about the Stackless mailing list