PEP 282: A Logging System -- comments please

[Aahz Maruch]

In article <3C894E28.BB2CCE7B at tds.net>, Edward K. Ream <edream at tds.net> wrote:
>
>PEP 282 talks about control flow, levels, loggers, handlers, formatters,
>filters and configuration.  A case can be made for dealing with each
>issue, and experience shows that simple dynamic tracing suffices in
>complex apps like compilers and file systems.  For example, all kinds of
>configuration (including picking formatters, data sinks, altering the
>flow of control of the program being run, etc.) can be done just by
>initializing the dict of tracepoint names.
>
>Dynamic tracing provides the essential benefit of any logging system,
>namely the ability to alter tracing output without altering the program
>being traced.  It does so in the simplest and most general way.

The problem that your solution fails to solve is the need for three
basic levels of output: debug, warn/info, error.  A single function may
want to provide all three levels, but users of that function may not
want to see all three all the time.  They will almost certainly want
error traces to be active almost all the time.
-- 
                      --- Aahz  <*>  (Copyright 2002 by aahz at pobox.com)

Hugs and backrubs -- I break Rule 6                 http://www.rahul.net/aahz/
Androgynous poly kinky vanilla queer het Pythonista

"Argue for your limitations, and sure enough they're yours."  --Richard Bach