Re: [ZODB-Dev] Re: [Zope-dev] Re: zLOG module deprecated
On 1/10/06, Andreas Jung <lists@andreas-jung.com> wrote:
This means basically keeping zLOG since it is only a very thin logging module wrapper. So why did we deprecate zLOG? :-)
Did we? It was implemented as a wrapper in 2.8, but wasn't officially deprecated until last week. ;-) I still have no opinion on the actual issue. I know what I want, but if it has too many drawbacks, I don't want it. :-) Something common between Zope3 and Zope2 would probably be a good idea. -- Lennart Regebro, Nuxeo http://www.nuxeo.com/ CPS Content Management http://www.cps-project.org/
--On 10. Januar 2006 12:20:14 +0100 Lennart Regebro <regebro@gmail.com> wrote:
On 1/10/06, Andreas Jung <lists@andreas-jung.com> wrote:
This means basically keeping zLOG since it is only a very thin logging module wrapper. So why did we deprecate zLOG? :-)
Did we? It was implemented as a wrapper in 2.8, but wasn't officially deprecated until last week. ;-)
Right, with the intention to get rid of zLOG at some point in the future (from my memory).
I still have no opinion on the actual issue. I know what I want, but if it has too many drawbacks, I don't want it. :-) Something common between Zope3 and Zope2 would probably be a good idea.
That would be the way to go. But I still have my doubts. Zope 3 obviously does not need a dedicated logging module, why does Zope 2 need one? Obviously ZEO (using TRACE) runs on Zope 3 without zLOG so specific extension can be handled locally. To bring this discussion to an end: - if we need specific logging functionaliy then it should be implemented to be shared between Zope 2 and Zope 3 - adjusting the current code base from 'logging' to zope.logging would mean just to replace the imports (assuming we keep getLogger() factory).... I am not totally against something like zope.logging but I still don't see the real need. We have some months until Zope 2.10 to get this in the right way. -aj
Andreas Jung wrote:
To bring this discussion to an end:
- if we need specific logging functionaliy then it should be implemented to be shared between Zope 2 and Zope 3
- adjusting the current code base from 'logging' to zope.logging would mean just to replace the imports (assuming we keep getLogger() factory)....
I am not totally against something like zope.logging but I still don't see the real need. We have some months until Zope 2.10 to get this in the right way.
Not requiring a new zope logging module (and using the builtin python logging module) helps keep the bar lower for python developers entering zope devleopment. Having to learn new standard log levels, etc raises that bar slightly. My personal opinion is to not introduce more zope packages when existing python modules are 99% sufficient. And removing existing zope packages (ie zLOG) when existing python modules are 99% sufficient is a "Very Good Thing" TM. So +1 on deprecating zLOG (and removing when possible) and not creating a new zope logging package. - Rocky -- Rocky Burt ServerZen Software -- http://www.serverzen.com ServerZen Hosting -- http://www.serverzenhosting.net News About The Server -- http://www.serverzen.net
participants (3)
-
Andreas Jung -
Lennart Regebro -
Rocky Burt