[issue34269] logging in 3.7 behaves different due to caching

Thomas Waldmann report at bugs.python.org
Sun Jul 29 05:03:56 EDT 2018


New submission from Thomas Waldmann <thomas.j.waldmann at gmail.com>:

When running the borgbackup tests on 3.7.0, quite some tests will be broken because expected log output is not emitted.

I traced this down up the point when I noticed that reverting the caching feature change of isEnabledFor method in Logger makes the tests work on 3.7.

I reviewed the logging code and the caching change, but could not easily find what is broken. There is of course some suspicion that cache invalidation might be the issue (it is present, but maybe it does not cover all the cases).

See there for more info:
https://github.com/borgbackup/borg/issues/3805

So, I suggest to first revert the caching feature change so we get a fixed logging in 3.7.1 and then to retry to add caching.

Note: I'm at EuroPython sprints today at the borgbackup table.

----------
messages: 322617
nosy: Thomas.Waldmann
priority: normal
severity: normal
status: open
title: logging in 3.7 behaves different due to caching
versions: Python 3.7

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


More information about the Python-bugs-list mailing list