killing thread ?

[Peter Hansen]

Paul Rubin wrote:
> 
> There's an entry in Python's bug tracking system on Sourceforge about
> supporting asynchronous exceptions in multi-threaded programs, showing
> the developers consider it something worth looking for ways to
> implement, rather than something that can't be done or something that
> shouldn't be done for portability reasons.
> 
> Since the new "minimal Python" is supposed to be stackless (all
> activation records are in the heap), maybe that implementation can
> more gracefully deal with the problem of killing a thread failing to
> unwind the C stack.

That would be a nice thought.  I doubt it would cleanly be able
to handle C extensions reliably though, but maybe ignoring some of
the limit cases would be acceptable for the value it provides in
the more common situations.

-Peter