[PEAK] peak logs

Phillip J. Eby pje at telecommunity.com
Thu Jan 1 23:16:23 EST 2004

At 10:06 PM 1/1/04 -0800, darryl wrote:
>Phillip J. Eby wrote:
>>At 07:33 PM 1/1/04 -0800, darryl wrote:
>>>As far as i can tell recent changes to peak logging has quietly
>>>broken all my logging :)
>>Could you be more specific as to what "broken" means in this case?
>>Thanks.  :)
>Ok, i get no logging anymore. Nada. Blank.  :)
>I dont' get an error of any kind.

I just tried to emulate your setup, by putting the config you gave into a 
file 'testcfg', then doing:

$ PEAK_CONFIG=testcfg PYTHONPATH=PEAK/src python
Python 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32
Type "help", "copyright", "credits" or "license" for more information.
 >>> from peak.api import *
 >>> logger=config.makeRoot().lookupComponent('logger:bots.jabber')
 >>> logger
<peak.running.logs.LogStream object at 0x00B4C3A0>
 >>> logger.level
 >>> logger.debug('test')
Jan 01 23:12:49 pje-2 bots.jabber[-142938727]: test

What happens when you do the same on your machine?

(By the way, the 'logs.LEVELNAME' constants are deprecated and will go away 
in a4.  Use e.g. 'levelName="DEBUG"' now instead when creating 
loggers.  This is unrelated to your problem, though, since I tried your 
configuration exactly as you presented it.)

More information about the PEAK mailing list