On 6/23/07, Vitaliyi <[EMAIL PROTECTED]> wrote: > Error in atexit._run_exitfuncs: > Traceback (most recent call last): > File "atexit.py", line 24, in _run_exitfuncs > func(*targs, **kargs) > File "threading.py", line 634, in __exitfunc > t.join() > File "threading.py", line 540, in join > self.__block.wait() > File "threading.py", line 203, in wait > waiter.acquire() > KeyboardInterrupt > Error in sys.exitfunc: > Traceback (most recent call last): > File "/usr/lib/python2.4/atexit.py", line 24, in _run_exitfuncs > func(*targs, **kargs) > File "/usr/lib/python2.4/threading.py", line 634, in __exitfunc > t.join() > File "/usr/lib/python2.4/threading.py", line 540, in join > self.__block.wait() > File "/usr/lib/python2.4/threading.py", line 203, in wait > waiter.acquire() > KeyboardInterrupt
This is a very strange set of tracebacks, as it seems that it has nothing to with BitTornado, instead only python2.4 files are listed (and the first ones don't have the full path, very strange indeed). I wonder if this could be a python2.4 bug. How long have you been seeing it? Does it occur with different versions of python? Can you upgrade to the latest python to test it, or try python 2.5 or python 2.3? Cameron -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
