On Nov.20, 2009 i got the traceback below from Python 3.1.1 under
WindowsXP-SP3, as several times before. From code with 

def _core(func, my_args):
    A = Thread(target = func, args = my_args); A.start(); A.join()
_core(ask_user, (question, default_answer))

Doesn't matter from what, the traceback is showing no calling line (thus
there is at least a slip in threading.py's exception handlers):

Unhandled exception in thread started by <bound method Thread._bootstrap
of <Thread(Thread-1, stopped 288)>>
Traceback (most recent call last):
  File "D:\Programme\Python31\lib\threading.py", line 482, in _bootstrap
    self._bootstrap_inner()
  File "D:\Programme\Python31\lib\threading.py", line 558, in
_bootstrap_inner
    self._stop()
  File "D:\Programme\Python31\lib\threading.py", line 569, in _stop
    self._block.notify_all()
  File "D:\Programme\Python31\lib\threading.py", line 273, in notify_all
    self.notify(len(self._waiters))
  File "D:\Programme\Python31\lib\threading.py", line 265, in notify
    for waiter in waiters:
TypeError: function takes exactly 1 argument (0 given)

Most probably better to ignore this. Sorry :(

The last line number 265 of the traceback is not the line causing the
error. This can be at quite another place, probably not in threading.py
- this is from code importing a new C-extension from me, who might
muddle the interpreter so terribly, that he is behaving like this
(unfortunately with code working very well on other opportunities).

I remember, that i had such a muddled interpreter with other problems
recently, and am working out now, what the real error might be (perhaps
missing Py_INCREFs). Still this is not the best behavior of the
interpreter, but one should not expect too much safety against
programming errors in C-extensions.

I wouldn't object a total deletion of this thread.