[issue34269] logging in 3.7 behaves different due to caching

[Thomas Waldmann]

Thomas Waldmann <thomas.j.waldmann at gmail.com> added the comment:

I agree that we should not dig that deep into logging internals and clear that dict from borg code.

But, seems like one has no public api to reinitialize logging to a like-fresh state, right? So maybe THAT is the real problem.

Add some .reset() method to do that?

BTW, removing that .clear() from our code made our tests work again. I am not sure why that was added in the first place as I could not find regressions after removing it.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34269>
_______________________________________