[Twisted-Python] Re: [Twisted-commits] r14614 - Describe log.debug, and 'printed' and 'debug' log dict items.

Itamar Shtull-Trauring itamar at itamarst.org
Tue Oct 4 15:06:18 EDT 2005

On Tue, 2005-10-04 at 10:00 -0700, Scott Lamb wrote:

> In my day job, I develop a lot of Java code. We have the luxury of  
> granular logging. I can switch, on a per-class basis, the output  
> level to trace, debug, warn, error, or fatal. That's handy.
> In Twisted, I see log.msg(), log.debug(), and log.err(). Why is one  
> of these levels going away? Is it just not normal to use logging for  
> debugging? What do you do instead?

twisted.python.log needs to be rewritten to support more modular
logging; the new API would be "log.msg(something, interface=IFoo)" where
IFoo might be IMessage, or IHTTPRequest for the webserver log, etc.. We
don't have thay yet, unfortunately. log.debug() as it works now is just
broken, it doesn't add anything to log.msg() in a reasonable way.

More information about the Twisted-Python mailing list