On Mon, Apr 7, 2008 at 8:40 PM, Greg Ewing <[EMAIL PROTECTED]> wrote: > Guido van Rossum wrote: > > Huh? We do that all the time. We won't let you control when memory is > > deallocated. > > I hardly think that being able to kill threads is > anywhere near as dangerous as being able to scribble > all over memory. And I *can* actually do that if I > really want, using ctypes. :-)
Killing threads at arbitrary points really is that dangerous. You can do it too, if you know the right APIs to access using ctypes. I'd love a magic solution to cleanly exiting a thread, but I don't think one is possible. You need some way to contain the insanity. Using a process is one. Using a side-effect-free language is another. Cancellation is a third option, and what I think will be the most convenient for python. -- Adam Olsen, aka Rhamphoryncus _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
