Tim Peters wrote:
We probably want an "ALL" level as well which would map to the "NOTSET"
of the Python logging code and log everything.
Why not call it NOTSET? Then you already have it ;-) Or forget it --
TRACE gets everything anyway.
Yeah, what he said ;-)
Also note that the code Florent pointed at is part of ZODB, not part
of Zope. Zope shouldn't use it directly. Growing its own copy would
be OK, or refactoring so that ZODB and Zope both get it from a shared
Sorry, which code are we talking about here?
Simplistix - Content Management, Zope & Python Consulting
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -