Vinay Sajip <vinay_sa...@yahoo.co.uk> added the comment: 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. ---------- assignee: -> vinay.sajip nosy: +vinay.sajip resolution: -> invalid status: open -> closed _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue7535> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
