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 Kylotan
Recipients Kylotan
Date 2007-12-10.15:23:13
SpamBayes Score 0.04059559
Marked as misclassified No
Message-id <1197300194.46.0.863908405505.issue1579@psf.upfronthosting.co.za>
In-reply-to
Content
The documentation for the logging module is quite confusing, and (I am
told) seems to assume prior experience with the log4j utility or similar.

In particular:
 - the front page has a rather confusing example of the named hierarchy
system, which might mislead the reader by making them think it's about
file types (perhaps for log output) rather than just arbitrary naming
conventions.
 - section 14.5.3 attempts to explain this hierarchy, but does so via an
example for something else (ie. showing logging to multiple
destinations), and is just a large code-dump, mixing several concepts in
one example.

All in all, it could just do with being a lot more explicit about how
the naming convention and the hierarchy works, how each logger relates
to children/parents, and having a more transparent example on the first
page.
History
Date User Action Args
2007-12-10 15:23:14Kylotansetspambayes_score: 0.0405956 -> 0.04059559
recipients: + Kylotan
2007-12-10 15:23:14Kylotansetspambayes_score: 0.0405956 -> 0.0405956
messageid: <1197300194.46.0.863908405505.issue1579@psf.upfronthosting.co.za>
2007-12-10 15:23:14Kylotanlinkissue1579 messages
2007-12-10 15:23:13Kylotancreate