[Python-Dev] Using logging in the stdlib and its unit tests (original) (raw)
Stephen J. Turnbull stephen at xemacs.org
Sat Dec 11 03:35:50 CET 2010
- Previous message: [Python-Dev] Using logging in the stdlib and its unit tests
- Next message: [Python-Dev] Using logging in the stdlib and its unit tests
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Glenn Linderman writes:
simple example for one file programs, include an example of specifying output severity threshold. I'm with Antoine here on my expectations.
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).
Maybe a small discussion of log formatting should be next? So the user realizes he shouldn't do the message formatting himself?
As advice, this shouldn't need to be more than a couple of lines, with a two line example, right? But it does deserve a prominent header.
- Then rotating logs for long-running programs.
And then the rest of the more feature-filled stuff.
+1 for this agenda.
- Previous message: [Python-Dev] Using logging in the stdlib and its unit tests
- Next message: [Python-Dev] Using logging in the stdlib and its unit tests
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]