Vinay Sajip added the comment:
Taking Brandon's advice re. creating a separate API.
However, note the reasons for not documenting all the attributes and hiding
them behind functions: logging's design pre-dates properties (it's of Python
1.5.2 vintage) and implementation details should remain
Brandon Craig Rhodes added the comment:
Adding an entirely separate API for introspection strikes me as
counter-productive — instead of merely having to maintain the logging API that
you already maintain, you will additionally now have an entirely separate and
second API that also has to be
Antoine Pitrou added the comment:
Perhaps you should explain what the point of this is.
--
nosy: +pitrou
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17855
___
R. David Murray added the comment:
I think that's what the link in the first message does. However, as I remember
Bradon's talk, the short answer is: make it easy to discover (and therefore
reason about) the hierarchy of logging objects that results from all the
logging setup calls in an
New submission from Vinay Sajip:
Track implementation of logger hierarchy introspection as per
http://plumberjack.blogspot.co.uk/2012/04/introspecting-logger-hierarchy.html
--
assignee: vinay.sajip
components: Library (Lib)
messages: 187904
nosy: vinay.sajip
priority: normal
severity:
Changes by Vinay Sajip vinay_sa...@yahoo.co.uk:
--
hgrepos: +186
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17855
___
___
Python-bugs-list
Changes by Vinay Sajip vinay_sa...@yahoo.co.uk:
--
keywords: +patch
Added file: http://bugs.python.org/file30032/64df448c183d.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17855
___
Vinay Sajip added the comment:
Added Brandon to nosy list, as his logging_tree is what set the ball rolling on
this one. Brandon, your comments on the patch would be very welcome.
--
nosy: +brandon-rhodes
stage: - patch review
___
Python tracker
