report at bugs
Nov 16, 2009, 3:23 PM
Post #1 of 2
(159 views)
Permalink
|
|
[issue7336] threading module not properly handling shutdown
|
|
New submission from R. Tyler Ballance <tyler [at] monkeypox>:
Receiving a traceback when shutting down an interpreter with threads
spawned inside of it:
Traceback (most recent call last):
File "/usr/lib/python2.6/threading.py", line 497, in __bootstrap
self.__bootstrap_inner()
File "/usr/lib/python2.6/threading.py", line 538, in __bootstrap_inner
(self.name, _format_exc()))
File "/usr/lib/python2.6/traceback.py", line 235, in format_exc
etype, value, tb = sys.exc_info()
AttributeError: 'NoneType' object has no attribute 'exc_info'
According to mzz on #Python:
17:29 < mzz> rtyler: I think this is worth a bug report. If you look up
threading.py:538 you'll find (assuming our line numbers match) that bit
of code actually goes out of its way to deal with the shutdown problem
I mentioned, but then it calls into the traceback module, which doesn't.
----------
components: Interpreter Core
messages: 95361
nosy: rtyler
severity: normal
status: open
title: threading module not properly handling shutdown
type: crash
versions: Python 2.6
_______________________________________
Python tracker <report [at] bugs>
<http://bugs.python.org/issue7336>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/list-python-bugs%40lists.gossamer-threads.com
|
