--On 10. Januar 2006 11:09:32 +0100 Lennart Regebro <[EMAIL PROTECTED]> wrote:
On 1/10/06, Andreas Jung <[EMAIL PROTECTED]> wrote:This decision was made for Zope 2.8 (according to zLOG/__init__.py).How do you mean? As far as I can see, all the levels are still there in zLOG py. The question now is weather two of these levels should be removed, as I understand it because you don't understand why other people use them. I find that logic difficult to understand.
""" This module exists only for backward compatibility. Any new code for Zope 2.8 and newer should use the logging module from Python's standard library directly. zLOG is only an API shim to map existing use of zLOG onto the standard logging API. """I don't read anything about using old log levels for new code. I read this as: use the Python logging module and if you need something special then implement it on your own. That's my interpretation.
Independent of the different interpretations: what is your suggestion? Leave the zLOG in place? Leave something else in place? Do we need commonZope logger architecture? Do we need one for Zope 2 and Zope 3? I still not getting the point why you can't use the logging module and extend if needed
inside your application or module? -aj
Description: PGP signature
_______________________________________________ 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 )