<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#330033" bgcolor="#ffffff">
On 12/10/2010 12:49 PM, Antoine Pitrou wrote:
<blockquote cite="mid:20101210214919.4ac63d27@pitrou.net"
type="cite">
<blockquote type="cite" style="color: rgb(0, 0, 0);">
<pre wrap="">And yet, I have helped many people who were baffled by exactly what
<span class="moz-txt-citetags">> </span>Bill observed: logging.info() didn't do anything. Maybe the default
<span class="moz-txt-citetags">> </span>should be INFO?
</pre>
</blockquote>
<pre wrap="">Funny, because displaying only errors and silencing other messages is
exactly what I expected logging to do by default.
</pre>
</blockquote>
<br>
So we are slowly learning the things that should be on the first
couple pages of the logging docs...<br>
<br>
1) simple example for one file programs, include an example of
specifying output severity threshold. I'm with Antoine here on my
expectations.<br>
<br>
2) example for multi-module, showing how a single logging
destination causes logging to happen in all modules, at the same
level (if that is the case, which I hope it is).<br>
<br>
3) Maybe a small discussion of log formatting should be next? So
the user realizes he shouldn't do the message formatting himself?<br>
<br>
4) Then rotating logs for long-running programs.<br>
<br>
And then the rest of the more feature-filled stuff. I agree logging
needs to be full-featured, but many of the features are only
necessary in complex environments, and simple stuff should be
simple, if it can be, and those cases explained first. Hopefully a
useful subset for simple cases can be described in 1-3 pages, and
then the complex features after that.<br>
</body>
</html>