On Thu, May 16 @ 20:36, Walter Dörwald wrote:
> > Then use
> > logging.setLoggerClass to ask the logging system to instantiate your own
> > logger class.
>
> ... which is done here. But this would change the LogRecord classes
> that are used on a global scale. I'd like to decide which class should
> be used when I'm creating the event. BTW, in setLoggerClass() you should
> probably use
> if not issubclass(klass, Logger):
> instead of
> if not (Logger in klass.__bases__):
Wish I had stumbled across this post before mine. +1 on this,
and I'm glad to hear it'll be included. Perhaps you might find
my set idea useful..
-- Mike
--
Michael Gilfix
mgilfix@eecs.tufts.edu
For my gpg public key:
http://www.eecs.tufts.edu/~mgilfix/contact.html
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