JoostBehrends <jo...@h-labahn.de> 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 <rep...@bugs.python.org> <http://bugs.python.org/issue7368> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
