Hi all, the zLOG module will be offically deprecated in Zope 2.10 (removed in Zope 2.12). New code _must_ use the 'logging' module of Python. And please help to replace all outstanding code that uses the zLOG module on the _trunk_ (which is a fun job :-|). Thanks, Andreas
Andreas Jung wrote at 2006-1-8 11:44 +0100:
the zLOG module will be offically deprecated in Zope 2.10 (removed in Zope 2.12). New code _must_ use the 'logging' module of Python. And please help to replace all outstanding code that uses the zLOG module on the _trunk_ (which is a fun job :-|).
If you deprecate "zLOG" could you please instruct the python logger to output Zope style tracebacks? Zope style tracebacks are much more informative than the stupid Python ones. As this is probably difficult without Monkey patching, I would prefer to have a Zope specific interface for logging purposes. -- Dieter
--On 8. Januar 2006 20:58:19 +0100 Dieter Maurer <dieter@handshake.de> wrote:
Andreas Jung wrote at 2006-1-8 11:44 +0100:
the zLOG module will be offically deprecated in Zope 2.10 (removed in Zope 2.12). New code _must_ use the 'logging' module of Python. And please help to replace all outstanding code that uses the zLOG module on the _trunk_ (which is a fun job :-|).
If you deprecate "zLOG" could you please instruct the python logger to output Zope style tracebacks?
Zope style tracebacks are much more informative than the stupid Python ones.
As this is probably difficult without Monkey patching, I would prefer to have a Zope specific interface for logging purposes.
We'll have to check that. Support in terms of patches are welcome :-) -aj
Andreas Jung wrote at 2006-1-8 22:14 +0100:
...
If you deprecate "zLOG" could you please instruct the python logger to output Zope style tracebacks?
Zope style tracebacks are much more informative than the stupid Python ones.
As this is probably difficult without Monkey patching, I would prefer to have a Zope specific interface for logging purposes.
We'll have to check that. Support in terms of patches are welcome :-)
The Zope specific interface for logging purposes is already there: You just want to deprecate and remove it. -- Dieter
--On 9. Januar 2006 20:06:09 +0100 Dieter Maurer <dieter@handshake.de> >> We'll have to check that. Support in terms of patches are welcome :-)
The Zope specific interface for logging purposes is already there:
You just want to deprecate and remove it.
_We_ want to _cleanup_ things. The current zLOG fascade does not provide any extra formatting code. So we are not giving anything away. The focus of Zope 2.10 is definitely on getting rid of old and redundant code, culprits etc. So old stuff will be deprecated and replaced code from Zope 3 where appliciable. -aj
Andreas Jung wrote:
the zLOG module will be offically deprecated in Zope 2.10 (removed in Zope 2.12). New code _must_ use the 'logging' module of Python. And please help to replace all outstanding code that uses the zLOG module on the _trunk_ (which is a fun job :-|).
If that is the case then I intend to: 1. move the definitions of zope's specific levels (trace and blather) into a more prominent place (ZODB also defines these levels, but it has to be an independent package), 2. rename 'blather' to 'verbose', 3. push back a number of framework logs that are done on every request at the trace level (as they were before the move to python's logging module), I'm thinking of transaction logs here. This leaves the 'debug' level free for application debugging. Florent -- Florent Guillaume, Nuxeo (Paris, France) CTO, Director of R&D +33 1 40 33 71 59 http://nuxeo.com fg@nuxeo.com
--On 9. Januar 2006 16:35:31 +0100 Florent Guillaume <fg@nuxeo.com> wrote:
If that is the case then I intend to: 1. move the definitions of zope's specific levels (trace and blather) into a more prominent place (ZODB also defines these levels, but it has to be an independent package),
ZODB defines these levels but I can not see any code in the ZODB package that actually uses these levels. -aj
[Andreas Jung]
ZODB defines these levels but I can not see any code in the ZODB package that actually uses these levels.
Nevertheless, grep'ing the ZODB source for TRACE and BLATHER will find them. TRACE is used only in modules under ZEO/zrpc/, and gives extremely verbose output about bare-metal ZEO communications. Only someone trying to debug low-level ZEO socket or protocol problems would want to use TRACE.
participants (4)
-
Andreas Jung -
Dieter Maurer -
Florent Guillaume -
Tim Peters