jeffrey yasskin ahzkvfwpgmailcom mon apr 7 2008 740 pm greg ewing wrote guido van rossum wrote maybe forked subprocess doesnt touch anything shared might taking returning large data structures would tedious transfer processes pickling might straightforward contain references objects dont want transfer want maintain references huh time wont let control memory deallocated hardly think able kill threads anywhere near dangerous able scribble memory actually really want using ctypes see three levels thread interruption first might want poke thread wake single system call thread might get back work afterwards resembles javas threadinterrupt second might want cancel thread ways let user clean afterward vaguely like pthread_cancel like threadinterrupt way clear interrupted status third might want really abort thread like javas threadstop uses three levels first implementation think pick one aborting unsafe situations vaguely remember josh block saying java hed make impossible clear threads interrupted status turning cancellation need check make sure got right im opposed theory providing really violent option say version provide plain cooperative cancellation 1 given library simulate calling threadingcancellation_point whatever name turns occasionally within inner loop 2 judging systems violent interruptions like posix signals haskell asynchronous exceptions well need way blocking aborts scope unblocking subscope namasté jeffrey yasskin _______________________________________________ python3000 mailing list python3000pythonorg httpmailpythonorgmailmanlistinfopython3000 unsubscribe httpmailpythonorgmailmanoptionspython3000python300040tangomucom thu 07 aug 2008 031814 0700 python3000 pythonsafethread project status