Basically, enable_test_log() sets log to a specific file (for the test suite), but disable_test_log pretty much universally calls 'enable_default_logging'. Which is okay for bzr itself, but other people calling our test suite will not use the same logging functionality.
(Most notably Launchpad :)
So there should be a better way such that enable/disable restores the original state. (Possibly by just updating the returned tuple to make it easier to restore the old settings)
Basically, enable_test_log() sets log to a specific file (for the test suite), but disable_test_log pretty much universally calls 'enable_ default_ logging' . Which is okay for bzr itself, but other people calling our test suite will not use the same logging functionality.
(Most notably Launchpad :)
So there should be a better way such that enable/disable restores the original state. (Possibly by just updating the returned tuple to make it easier to restore the old settings)