On 09/08/06, Georg Brandl <g.brandl at gmx.net> wrote: > Is this considered a bug? Sure, deleting modules from sys.modules > isn't quite common, but it happened to me on one occasion. > > Python 2.4.3 (#1, Jul 29 2006, 10:52:20) > >>> import logging > >>> import sys > >>> del logging > >>> del sys.modules['logging'] > >>> ^D > Error in atexit._run_exitfuncs: > Traceback (most recent call last): > File "/usr/lib/python2.4/atexit.py", line 24, in _run_exitfuncs > func(*targs, **kargs) > File "/usr/lib/python2.4/logging/__init__.py", line 1328, in shutdown > for h in _handlerList[:]: # was _handlers.keys(): > TypeError: unsubscriptable object > Error in sys.exitfunc: > Traceback (most recent call last): > File "/usr/lib/python2.4/atexit.py", line 24, in _run_exitfuncs > func(*targs, **kargs) > File "/usr/lib/python2.4/logging/__init__.py", line 1328, in shutdown > for h in _handlerList[:]: # was _handlers.keys(): > TypeError: unsubscriptable object > > Obviously, _handlerList (as a global) is already cleaned up, which is why > the subscript fails. > > Georg > > _______________________________________________ Could it be considered a bug in the atexit module (or is that what you meant)? Seeing as there's no _decent_ way to recover from this error, perhaps it could just slip silently passed? -- Matt http://mattssanctuary.blogspot.com
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4