On Dec 9, 2007 6:38 PM, Ben Sizer <[EMAIL PROTECTED]> wrote: > I consider those docs to be among the worst in the entire Python > library.
Part of the problem is likely that they assume some level of familiarity with the "log4" logging architecture. This is the most common set of logging patterns around: Java has log4j, C++ has log4cpp and log4cxx, etc. If you've used one of these before, then the docs are pretty clear; otherwise, they're not. In the example you noted, "scan.html" is more likely to mean the "logger for a scanner object that parses html files", rather "the logger that logs messages intended to go to an html file". But I agree that it might be confusing--would you mind logging a bug at http://bugs.python.org/? > I would really just like to see a little more clarification on what > Turbogears sets up for you by default, and less reliance on someone > having read through all the logging module documentation (especially > given that the TG page suggests you only need to understand the first > page). Both reasonable. -- Tim Lesher <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
