[Zope-Coders] Zope Bugs, Features, and Patches Collector: Open Issues

2005-04-06 Thread tseaver
The following supporters have open issues assigned to them in this collector (http://www.zope.org/Collectors/Zope). Assigned and Open Brian - "ZPT not being processed with text/vnd.wap.wml mime type", [Accepted] http://www.zope.org/Collectors/Zope/968 Caseman - "ZCTextUndex

[Zope-Coders] Zope tests: 6 OK

2005-04-06 Thread Zope tests summarizer
Summary of messages to the zope-tests list. Period Tue Apr 5 11:01:01 2005 UTC to Wed Apr 6 11:01:01 2005 UTC. There were 6 messages: 6 from Zope Unit Tests. Tests passed OK --- Subject: OK : Zope-2_6-branch Python-2.1.3 : Linux From: Zope Unit Tests Date: Tue Apr 5 22:43:07 EDT 2

[Zope-Coders] Zope 2.7.6 release schedule

2005-04-06 Thread Andreas Jung
The schedule for the next Zope release is a follows: 2.7.6 b1: April 13th 2.7.6 RC1: April 20th 2.7.6 final: April 27th Although 2.7.5 had been relased lately, yesterdays hotfix and another bug justify a new release this month. Andreas pgpUdi8AIHsLz.pgp Description: PGP signature __

[Zope-Coders] Logging and Zope 2.8

2005-04-06 Thread Sidnei da Silva
Anyone has enough knowledge about the zLOG changes in Zope 2.8 to give a clue about why it's logging much more stuff to the console and the output looks sooo different? -- Sidnei da Silva <[EMAIL PROTECTED]> http://awkly.org - dreamcatching :: making your dreams come true http://www.enfoldsys

[Zope-Coders] Re: Logging and Zope 2.8

2005-04-06 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sidnei da Silva wrote: > Anyone has enough knowledge about the zLOG changes in Zope 2.8 to give > a clue about why it's logging much more stuff to the console and the > output looks sooo different? Zope 2.8 uses the standard Python 'logger' module

Re: [Zope-Coders] Re: Logging and Zope 2.8

2005-04-06 Thread Jens Vagelpohl
On Apr 7, 2005, at 2:09, Tres Seaver wrote: At "INFO" level, I think 2.8 logs even less than 2.7; "BLATHER" level is a lot noiser, however. I have no earthly idea why we default the logging level to "all" (but 2.7 did to); "INFO" is a much more reasonable default. Yes, that logging level "all" sh