New submission from Jack Jansen <jack.jan...@cwi.nl>:
The logging module and its API make it easy to modify the behaviour of all loggers used in any package in your program. Unfortunately the downside of this is that if any author of any module that you use changes the global logger configuration you get in a situation where all your logger calls are not behaving as expected. Moreover, it is very difficult to debug this and to find the culprit. If the logger module had a global "debug logger usage" flag which would make it emit a log message whenever a call changed the global configuration this would help, especially if the messages were vectored through a single function or method that you could then set a breakpoint on. ---------- components: Library (Lib) messages: 376308 nosy: jackjansen priority: normal severity: normal status: open title: logging module needs some form of introspection or debugging support type: enhancement versions: Python 3.8 _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue41704> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
