See PEP 282 [1]. If this PEP is accepted, work should probably follow its course. It would be nice to have a single logging mechanism for Python, and for Zope to use and/or extend it. Granted, if it is accepted, it won't be in Python until Python 2.3 which I believe is due in August.
..[1] http://python.sourceforge.net/peps/pep-0282.html On 2/28/02 3:34 PM, "Romain Slootmaekers" <[EMAIL PROTECTED]> wrote: > > Yo, > questions wrt logging: > > -) What are the plans to improve the rather primitive logging facilities > in zope ? > I couldn't find anything in the plan for 2.6, nor on the 3.0 homepage. > I think we need at least an extendibl framework with following types of > components: > > - Loggers (fi, file logger, db loggers, remote logger, nulllogger,...) > - Filters (fi on severity, on subsystem, ...) > - LogBus (central accesspoint for the logging framework, > where you can (dynamically) hook your loggers, filters etc... > > if time is an issue, we could just copy the design of fi Log4J which is a > good logging framework for apache. > > -) If there are no such plans, can we hack something up ourselves and > add/donate it to the product ? I hate writing stuff that gets replaced by > something else afterwards .... > > input appreciated. > > Sloot. -- Jeffrey P Shell www.cuemedia.com _______________________________________________ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )