This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author sblondon
Recipients sblondon
Date 2021-09-03.17:01:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1630688509.83.0.0453605836271.issue45095@roundup.psfhosted.org>
In-reply-to
Content
Currently, logging.root.manager.loggerDict is usable to do a homemade traversal of the loggers tree. However, it's not a public interface. Adding a 'logger.getChildren()' method would help to implement the traversal. The method would return a set of loggers.


Usage example:
>>> import logging
>>> logging.basicConfig(level=logging.CRITICAL)
>>> root_logger = logging.getLogger()
<RootLogger root (CRITICAL)>
>>> root_logger.getChildren()
set()
>>> a_logger = logging.getLogger("a")
>>> root_logger.getChildren()
{<Logger a. (CRITICAL)>}
>>> logging.getLogger('a.b').setLevel(logging.DEBUG)
>>> _ = logging.getLogger('a.c')
>>> a_logger.getChildren()
{<Logger a.c (CRITICAL)>, <Logger a.b (DEBUG)>}


With such method, traverse the tree will be obvious to write with a recursive function.


Use cases:
 - to check all the loggers are setted up correctly. I wrote a small function to get all loggers, and log on every level to check the real behaviour.
 - to draw the loggers tree like logging_tree library (https://pypi.org/project/logging_tree/). I didn't ask to logging_tree's maintainer but I don't think he would use such function because the library works for huge range of python releases.


I plan to write a PR if someone thinks it's a good idea.
History
Date User Action Args
2021-09-03 17:01:49sblondonsetrecipients: + sblondon
2021-09-03 17:01:49sblondonsetmessageid: <1630688509.83.0.0453605836271.issue45095@roundup.psfhosted.org>
2021-09-03 17:01:49sblondonlinkissue45095 messages
2021-09-03 17:01:49sblondoncreate