[Python-Dev] Recent logging spew

[Tim Peters]

We're getting an awful lot of these turds at the ends of test runs now:

Error in atexit._run_exitfuncs:
Traceback (most recent call last):
  File "C:\Code\bb_slave\trunk.peters-windows\build\lib\atexit.py",
line 24, in _run_exitfuncs
    func(*targs, **kargs)
  File "C:\Code\bb_slave\trunk.peters-windows\build\lib\logging\__init__.py",
line 1351, in shutdown
    h.flush()
  File "C:\Code\bb_slave\trunk.peters-windows\build\lib\logging\__init__.py",
line 731, in flush
    self.stream.flush()
ValueError: I/O operation on closed file
Error in sys.exitfunc:
Traceback (most recent call last):
  File "C:\Code\bb_slave\trunk.peters-windows\build\lib\atexit.py",
line 24, in _run_exitfuncs
    func(*targs, **kargs)
  File "C:\Code\bb_slave\trunk.peters-windows\build\lib\logging\__init__.py",
line 1351, in shutdown
    h.flush()
  File "C:\Code\bb_slave\trunk.peters-windows\build\lib\logging\__init__.py",
line 731, in flush
    self.stream.flush()
ValueError: I/O operation on closed file
[450168 refs]
program finished with exit code 0

Not sure what caused it, but suspect this:

"""
Author: georg.brandl
Date: Fri Aug 11 09:26:10 2006
New Revision: 51206

Modified:
  python/trunk/Lib/logging/__init__.py
  python/trunk/Misc/NEWS
Log:
logging's atexit hook now runs even if the rest of the module has
already been cleaned up.
"""

Anyway, can we stop this?  It doesn't look like "a feature" from here ;-)