Michael Chermside writes: > Seems like an uncommon request, but one which shouldn't be made > impossible for those who want it. But couldn't it be achieved by > writing a handler which simply re-logged the message at the new > spot in the hierarchy? That would solve that use case handily; if that's the right approach, such a handler should be provided as part of the standard set of handlers. The use case for a .setlogger() method on the various objects that perform logging is different, so that is still needed. Generally, I'm not convinced that a getdefaultlogger() is needed or helpful (it seems an implementation default for the module), though I'm not at all opposed to the setdefaultlogger() for the affected modules. -Fred -- Fred L. Drake, Jr. <fdrake at acm.org> PythonLabs at Zope Corporation
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4