summaryrefslogtreecommitdiffhomepage
path: root/README
diff options
context:
space:
mode:
authorRobey Pointer <robey@lag.net>2004-03-08 09:47:47 +0000
committerRobey Pointer <robey@lag.net>2004-03-08 09:47:47 +0000
commitc565d66e390f613f776146665bebbe63a163b0e2 (patch)
treed4af8a3851e88cab7a1b42eae2ecdb0196f4dd5b /README
parent3e31771637cb87e2cae2092121562b47ea13cd6e (diff)
[project @ Arch-1:robey@lag.net--2003-public%secsh--dev--1.0--patch-28]
fix lingering thread bug this bug has been in there forever and i could never figure out a workaround till now. when the python interpreter exits, it doesn't necessarily destroy the remaining objects or call __del__ on anything, and it will lock up until all threads finish running. how the threads are supposed to notice the exiting interpreter has always been sort of a mystery to me. tonight i figured out how to use the 'atexit' module to register a handler that runs when the interpreter exits. now we keep a list of active threads and ask them all to exit on shutdown. no more going to another shell to kill -9 python! yeah!!
Diffstat (limited to 'README')
0 files changed, 0 insertions, 0 deletions