adam olsen kjbnfagmailcom tue apr 8 2008 446 pm greg ewing wrote adam olsen wrote killing threads arbitrary points really dangerous im talking killing arbitrary thread particular thread ive designed idea killing mind im really talking killing either way tapping shoulder getting attention whatever happens dont believe thats outrageously unreasonable thing want able precise mind 1 way causing exception raised asynchronously another thread 2 exceptions would automatically blocked finally clause 3 would way explicitly blocking around section code eg using context manager 4 makes anyone feel better could blocked default explicitly enabled thread concerned 5 thread dies either locks holding automatically released b exception raised main thread dies holding locks since indicates programming error ie thread failed clean receiving asynchronous exception anyone point reason would difficult write wellbehaved threaded code presence features think bothers want restrictions enforced upfront violation produces clear exception whereas proposal diagnose later counter proposal could either forbid acquiring locks implicitly block asynchronous exception also worth noting little info given operation subdivided personally think thats good thing need youre something wrong two use cases mind 1 cpu bound tasks cant subdivided 101010 2 arbitrary code interactive interpreter latter cant done sanely simply accepting hung interpreter possibly unlikely corrupted user program wed rather risk corrupting user program adam olsen aka rhamphoryncus _______________________________________________ python3000 mailing list smsbmo9552pythonorg httpmailpythonorgmailmanlistinfopython3000 unsubscribe httpmailpythonorgmailmanoptionspython3000python300040tangomucom thu 07 aug 2008 051058 0600 python3000 pythonsafethread project status