January 2006 - Zope-Dev

Re: [ZODB-Dev] Re: [Zope-dev] Re: zLOG module deprecated
by Tim Peters 10 Jan '06

10 Jan '06

[Andreas Jung] > ... > Obviously ZEO (using TRACE) runs on Zope 3 without zLOG so specific > extension can be handled locally. ZEO also runs on Zopes 2.8 and 2.9 without zLOG -- zLOG hasn't been used in ZODB since 3.2 (ZODBs 3.3, 3.4, 3.5, 3.6, and current trunk contain no references to zLOG). If Zope folk generally want more than the 5 logging levels that come built in to Python's logging module, that's easy to supply, but then it's also important that they define them with the same names and numeric values. ZODB's loglevels.py does so, and is the only "extension" to Python's logging module ZODB made. This is the code in its entirety (but skipping the copyright boilerplate at the top -- Copyright (c) 2004 Zope Corporation and Contributors): """ import logging __all__ = ["BLATHER", "TRACE"] # 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) # TRACE (-300) none -- defined here as TRACE (5) # # TRACE is used by ZEO for extremely verbose trace output, enabled only # when chasing bottom-level communications bugs. It really should be at # a lower level than DEBUG. # # BLATHER is a harder call, and various instances could probably be folded # into INFO or DEBUG without real harm. BLATHER = 15 TRACE = 5 logging.addLevelName("BLATHER", BLATHER) logging.addLevelName("TRACE", TRACE) """ When ZODB wants to use BLATHER or TRACE, it imports the symbolic name from ZODB.loglevels instead of from logging. That's all there is to it -- it's trivial. If Zope decided to keep BLATHER and TRACE too, then a future ZODB release would presumably change to import BLATHER and TRACE from the same place Zope gets them.

1 0

Re: [ZODB-Dev] Re: [Zope-dev] Re: zLOG module deprecated
by Lennart Regebro 10 Jan '06

10 Jan '06

On 1/9/06, Andreas Jung <lists(a)andreas-jung.com> wrote: > I've never had the need to use them. No, but other people do. > That's different from not wanting to > use them. The more choice you have, the more trouble you have. I agree that > a TRACE level might be of interest. But BLATHER and PROBLEM is competely > overhead from my point of view - in fact I can't explain when to use > BLATHER or TRACE compared to DEBUG. But I can, and so can Florent. "PROBLEM" I agree about. I have never heard that one before, and I don't see why you can't use ERROR or WARNING. ERROR: Something didn't work. WARNING: There is something fishy here, I'm guessing how it should be handled. INFO: Nothing is wrong, but this is important. (For example Zope server ready to handle requests). VERBOSE: Nothing is wrong and this may be important. (For example the info saying what IP-adress and port the zope server is started on.) DEBUG: For debug information. TRACE: I need to have a lot of information now! I find all this fairly self-evident and highly useful, and se absolutely zero reason for removing them, when they are so useful. -- Lennart Regebro, Nuxeo http://www.nuxeo.com/ CPS Content Management http://www.cps-project.org/

3 2

Zope tests: 8 OK
by Zope tests summarizer 10 Jan '06

10 Jan '06

Summary of messages to the zope-tests list. Period Mon Jan 9 12:01:02 2006 UTC to Tue Jan 10 12:01:02 2006 UTC. There were 8 messages: 8 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2_6-branch Python-2.1.3 : Linux From: Zope Unit Tests Date: Mon Jan 9 21:02:54 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/003970.html Subject: OK : Zope-2_6-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Mon Jan 9 21:04:25 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/003971.html Subject: OK : Zope-2_7-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Mon Jan 9 21:05:55 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/003972.html Subject: OK : Zope-2_7-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Mon Jan 9 21:07:25 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/003973.html Subject: OK : Zope-2_8-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Mon Jan 9 21:08:55 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/003974.html Subject: OK : Zope-2_8-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Mon Jan 9 21:10:25 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/003975.html Subject: OK : Zope-2_9-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Mon Jan 9 21:11:56 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/003976.html Subject: OK : Zope-trunk Python-2.4.2 : Linux From: Zope Unit Tests Date: Mon Jan 9 21:13:26 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/003977.html

1 0

Re: [ZODB-Dev] Re: [Zope-dev] Re: zLOG module deprecated
by Lennart Regebro 10 Jan '06

10 Jan '06

On 1/10/06, Andreas Jung <lists(a)andreas-jung.com> wrote: > I don't read anything about using old log levels for new code. And neither do I read anything about NOT using them. So, your statement that the decision was taken in 2.8 is false. That renders the last posts pointless, and we are back at my first post about the levels today. > Independent of the different interpretations: what is your suggestion? I don't have an opinion on solution yet. What I want is something easy to use wher you can just import a log method or object and make a function. I don't want to set things up, because if we need to set things up, everybody will set things up differently, which is not a good idea. -- Lennart Regebro, Nuxeo http://www.nuxeo.com/ CPS Content Management http://www.cps-project.org/

2 1

zLOG module deprecated
by Andreas Jung 09 Jan '06

09 Jan '06

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

4 7

Re: SVN: Zope/trunk/lib/python/StructuredText/ Sanely deprecate StructuredText by making it a facade of zope.structuredtext.
by Florent Guillaume 09 Jan '06

09 Jan '06

Philipp von Weitershausen wrote: > Log message for revision 41225: > Sanely deprecate StructuredText by making it a facade of zope.structuredtext. > Just to make sure: we didn't lose the "ReST allowed arbitrary file includes" bugfix by doing this? Florent -- Florent Guillaume, Nuxeo (Paris, France) CTO, Director of R&D +33 1 40 33 71 59 http://nuxeo.com fg(a)nuxeo.com

2 2

Twice-annual releases and bugfixes?
by Jeff Kowalczyk 09 Jan '06

09 Jan '06

What does the twice-annual release policy say about bugs and/or packaging errors that are identified and fixed within a very short time of the official release announcement? Log message for revision 41228: Merge r41227 from 2.9 branch: Update Five to bugfix release 1.3.1. Changed: U Zope/trunk/lib/python/Products/Five/CHANGES.txt U Zope/trunk/lib/python/Products/Five/site/localsite.py U Zope/trunk/lib/python/Products/Five/site/tests/sitemanager.txt U Zope/trunk/lib/python/Products/Five/tests/adapters.py U Zope/trunk/lib/python/Products/Five/version.txt (...) +* Fix an adapter look-up bug in the local site implementation +that was due to an oversight during the port to Zope 3.2. I'm building from svn, so it doesn't make much difference to me, but I was curious whether the circumstances (if any) that would trigger bugfix releases were documented anywhere.

5 4

buildbot failure in Zope branches 2.9 2.4 Linux zc-buildbot
by buildbot＠zope.com 09 Jan '06

09 Jan '06

The Buildbot has detected a failed build of Zope branches 2.9 2.4 Linux zc-buildbot. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 2687 Blamelist: Zen,andreasjung,jim,oestermeier,yuppie BUILD FAILED: failed test sincerely, -The Buildbot

1 0

Zope tests: 7 OK, 1 Failed
by Zope tests summarizer 09 Jan '06

09 Jan '06

Summary of messages to the zope-tests list. Period Sun Jan 8 12:01:01 2006 UTC to Mon Jan 9 12:01:01 2006 UTC. There were 8 messages: 8 from Zope Unit Tests. Test failures ------------- Subject: FAILED (errors=2) : Zope-2_8-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Sun Jan 8 21:08:17 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/003966.html Tests passed OK --------------- Subject: OK : Zope-2_6-branch Python-2.1.3 : Linux From: Zope Unit Tests Date: Sun Jan 8 21:02:17 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/003962.html Subject: OK : Zope-2_6-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Sun Jan 8 21:03:47 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/003963.html Subject: OK : Zope-2_7-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Sun Jan 8 21:05:17 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/003964.html Subject: OK : Zope-2_7-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Sun Jan 8 21:06:47 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/003965.html Subject: OK : Zope-2_8-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Sun Jan 8 21:09:48 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/003967.html Subject: OK : Zope-2_9-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Sun Jan 8 21:11:18 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/003968.html Subject: OK : Zope-trunk Python-2.4.2 : Linux From: Zope Unit Tests Date: Sun Jan 8 21:12:48 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/003969.html

1 0

buildbot failure in Zope trunk 2.4 Linux zc-buildbot
by buildbot＠zope.com 08 Jan '06

08 Jan '06

The Buildbot has detected a failed build of Zope trunk 2.4 Linux zc-buildbot. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 2670 Blamelist: andreasjung BUILD FAILED: failed test sincerely, -The Buildbot

1 0