Leonardo Rochael Almeida added the comment:
At the very least this is a documentation bug. By reading the std docs
on the logging module [1] one gets the impression that if a log record
gets to a certain logger, even if percolated from more specific loggers,
then the filters to that logger
New submission from Leonardo Rochael Almeida :
A filter added to, say, logging.getLogger('a').addFilter() never gets
the chance to filter messages logged into logging.getLogger('a.b').
On logging.Logger.handle() the current logger filters are called to
check if the message
