We probably want an "ALL" level as well which would map to the "NOTSET" of the Python logging code and log everything.
Florent, I don't see a TRACE level in this list. Did you think one was needed? On Mon, 5 Dec 2005, Florent Guillaume wrote: > Chris Withers wrote: > >> # In the days of zLOG, there were 7 standard log levels, and > >> ZODB/ZEO used > >> # all of them. Here's how they map to the logging package's 5 > >> standard > >> # levels: > >> # > >> # zLOG logging > >> # ------------- --------------- > >> # PANIC (300) FATAL, CRITICAL (50) > >> # ERROR (200) ERROR (40) > >> # WARNING, PROBLEM (100) WARN (30) > >> # INFO (0) INFO (20) > >> # BLATHER (-100) none -- defined here as BLATHER (15) > >> # DEBUG (-200) DEBUG (10) > > > > > > imnsho, blather and debug are the wrong way round. blather should go > > away completely, it's a stupid name anyway :-( > > Just because you don't see the use in something doesn't mean it has to go > away. > > In my book BLATHER is used for "verbose INFO" and is different than DEBUG > and TRACE (both levels are useful too). INFO and BLATHER are for the > administrator. DEBUG and TRACE are for the developer. > > Florent > > -- _______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )