Following a selftest run with Python 2.7 there's some new junk printed at the end that's not present with earlier Python versions. Perhaps related to a change in the logging module?
Error in atexit._run_exitfuncs:
Traceback (most recent call last):
File ".\lib\atexit.py", line 24, in _run_exitfuncs
func(*targs, **kargs)
File ".\lib\logging\__init__.py", line 1615, in shutdown
h.flush()
File ".\lib\logging\__init__.py", line 824, in flush
self.stream.flush()
ValueError: I/O operation on closed file
Traceback (most recent call last):
File "bzr", line 153, in <module>
sys.exitfunc()
File ".\lib\atexit.py", line 24, in _run_exitfuncs
func(*targs, **kargs)
File ".\lib\logging\__init__.py", line 1615, in shutdown
h.flush()
File ".\lib\logging\__init__.py", line 824, in flush
self.stream.flush()
ValueError: I/O operation on closed file
Exception TypeError: "'NoneType' object is not callable" in <function _removeHandlerRef at 0x00CC3E70> ignored
So, this is an upstream regression, but it's only exposed because of my favourite bazaar testing regression from the introduction of the testtools dependency. In short, TestCase attributes are no longer cleared after being run, so the _log_memento which holds, amongst other things, a reference to the logging StreamHandler sticks around until python exits.
So, cleaning up some testing cruft is an easy fix. However, I wonder whether Bazaar shouldn't follow the FIXME at the top of the bzrlib.trace and remove the use of the logging module entirely.