Message96525
This behaviour is by design. Messages logged to logger 'a.b' are not
passed to logger 'a' - they are passed to *the handlers* of logger 'a'
(and so on up until a false value is seen for the logger's 'propagate'
attribute). In this respect, filtering works in the same way as levels
do - for example if logger 'a' has a level of WARNING and logger 'a.b'
has a level of DEBUG, then DEBUG events logged to 'a.b' will still show
up in the logs.
Closing, as it's not a bug, and implementing the alternative would not
be backwards compatible. |
|
Date |
User |
Action |
Args |
2009-12-17 19:20:17 | vinay.sajip | set | recipients:
+ vinay.sajip, leorochael |
2009-12-17 19:20:17 | vinay.sajip | set | messageid: <1261077617.61.0.295014465553.issue7535@psf.upfronthosting.co.za> |
2009-12-17 19:20:16 | vinay.sajip | link | issue7535 messages |
2009-12-17 19:20:15 | vinay.sajip | create | |
|