[issue14474] mishandling of AttributeError in threads

Stefan Behnel added the comment: Could the while thread._count() > c: pass in test_thread.py be changed to this? (as used in other places) while thread._count() > c: time.sleep(0.01) It currently hangs in Cython because it doesn't free the GIL during the plain C loop

[issue14474] mishandling of AttributeError in threads

Roundup Robot added the comment: New changeset 60ad83716733 by Benjamin Peterson in branch '3.2': prevent writing to stderr from messing up the exception state (closes #14474) http://hg.python.org/cpython/rev/60ad83716733 -- ___ Python tracker

[issue14474] mishandling of AttributeError in threads

Roundup Robot added the comment: New changeset 8609d7fcdcc7 by Benjamin Peterson in branch '2.7': prevent writing to stderr from messing up the exception state (closes #14474) http://hg.python.org/cpython/rev/8609d7fcdcc7 -- nosy: +python-dev resolution: -> fixed stage: -> committed/r

[issue14474] mishandling of AttributeError in threads

Pierre Ossman added the comment: Indeed. I assume old style classes are still supported though? -- ___ Python tracker ___ ___ Python-

[issue14474] mishandling of AttributeError in threads

Amaury Forgeot d'Arc added the comment: If Dummy is a new-style class, the traceback is correctly printed. -- nosy: +amaury.forgeotdarc ___ Python tracker ___ __

[issue14474] mishandling of AttributeError in threads

New submission from Pierre Ossman : These three things do not mix: - AttributeError - Threads - Object methods An unhandled AttributeError thrown in a thread will not call sys.excepthook if the thread's start function is a class/object method. Test case: import sys import thread class D