Mailing List Archive: Python: Bugs

[issue7368] Internal error in threading.py

Index | Next | Previous | View Threaded

report at bugs

Nov 20, 2009, 5:22 AM

Post #1 of 3 (194 views)
Permalink

[issue7368] Internal error in threading.py

New submission from JoostBehrends <joost [at] h-labahn>:

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)

----------
components: Library (Lib)
messages: 95539
nosy: 3Jane
severity: normal
status: open
title: Internal error in threading.py
type: compile error
versions: Python 3.1

_______________________________________
Python tracker <report [at] bugs>
<http://bugs.python.org/issue7368>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/list-python-bugs%40lists.gossamer-threads.com

report at bugs

Nov 20, 2009, 7:11 AM

Post #2 of 3 (182 views)
Permalink

[issue7368] Internal error in threading.py [In reply to]

JoostBehrends <joost [at] h-labahn> added the comment:

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.

----------

_______________________________________
Python tracker <report [at] bugs>
<http://bugs.python.org/issue7368>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/list-python-bugs%40lists.gossamer-threads.com

report at bugs

Nov 20, 2009, 8:08 AM

Post #3 of 3 (178 views)
Permalink

[issue7368] Internal error in threading.py [In reply to]

Changes by R. David Murray <rdmurray [at] bitdance>:

----------
priority: -> normal
resolution: -> invalid
stage: -> committed/rejected
status: open -> closed
type: compile error -> behavior

_______________________________________
Python tracker <report [at] bugs>
<http://bugs.python.org/issue7368>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/list-python-bugs%40lists.gossamer-threads.com

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads