[Python-Dev] Consistent logging in the standard library (original) (raw)
Fred L. Drake, Jr. fdrake at acm.org
Wed Sep 10 13:04:07 EDT 2003
- Previous message: [Python-Dev] Consistent logging in the standard library
- Next message: [Python-Dev] Consistent logging in the standard library
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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. PythonLabs at Zope Corporation
- Previous message: [Python-Dev] Consistent logging in the standard library
- Next message: [Python-Dev] Consistent logging in the standard library
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]