June 2008 - Zope-Dev

Zope Tests: 5 OK
by Zope Tests Summarizer 10 Jun '08

10 Jun '08

Summary of messages to the zope-tests list. Period Mon Jun 9 11:00:00 2008 UTC to Tue Jun 10 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Mon Jun 9 20:59:28 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009680.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Mon Jun 9 21:00:59 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009681.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Mon Jun 9 21:02:29 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009682.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Mon Jun 9 21:04:00 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009683.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Mon Jun 9 21:05:30 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009684.html

1 0

buildbot failure in Zope on zc.queue
by ct＠gocept.com 10 Jun '08

10 Jun '08

The Buildbot has detected a new failure of zc.queue on Zope. Full details are available at: http://zopebuildbot.whq.gocept.com/zc.queue/builds/89 Buildbot URL: http://zopebuildbot.whq.gocept.com/ Buildslave for this Build: local Build Reason: The Nightly scheduler named 'zc.queue nightly' triggered this build Build Source Stamp: [branch zc.queue/trunk] HEAD Blamelist: BUILD FAILED: failed svn Logs are attached. sincerely, -The Buildbot

1 0

buildbot failure in Zope on z3c.recipe.subprocess
by ct＠gocept.com 10 Jun '08

10 Jun '08

The Buildbot has detected a new failure of z3c.recipe.subprocess on Zope. Full details are available at: http://zopebuildbot.whq.gocept.com/z3c.recipe.subprocess/builds/90 Buildbot URL: http://zopebuildbot.whq.gocept.com/ Buildslave for this Build: local Build Reason: The Nightly scheduler named 'z3c.recipe.subprocess nightly' triggered this build Build Source Stamp: [branch z3c.recipe.subprocess/trunk] HEAD Blamelist: BUILD FAILED: failed svn Logs are attached. sincerely, -The Buildbot

1 0

buildbot failure in Zope on z3c.traverser
by ct＠gocept.com 09 Jun '08

09 Jun '08

The Buildbot has detected a new failure of z3c.traverser on Zope. Full details are available at: http://zopebuildbot.whq.gocept.com/z3c.traverser/builds/91 Buildbot URL: http://zopebuildbot.whq.gocept.com/ Buildslave for this Build: local Build Reason: The Nightly scheduler named 'z3c.traverser nightly' triggered this build Build Source Stamp: [branch z3c.traverser/trunk] HEAD Blamelist: BUILD FAILED: failed test Logs are attached. sincerely, -The Buildbot

2 1

Re: [Checkins] SVN: zc.buildout/branches/plus-minus-option-syntax-for-review/src/zc/buildout/buildout. A patch contributed by Mustapha Benali that provide - and + prefix operators for buildout configuration option values; this allow adding and removing option values to an already existing section option (applicable when extending configuration files). See also: http://answers.edge.launchpad.net/zc.buildout/+question/35159.
by Stefan H. Holek 09 Jun '08

09 Jun '08

Shouldn't this read ".. += and -= operators."? Stefan On 05.06.2008, at 19:58, Malthe Borch wrote: > +Adding and removing options > +--------------------------- > + > +We can append and remove values to an option by using the + and - > +operators. > + > +This is illustrated below; first we define a base configuration. -- Stefan H. Holek stefan(a)epy.co.at

1 0

Zope Tests: 5 OK
by Zope Tests Summarizer 09 Jun '08

09 Jun '08

Summary of messages to the zope-tests list. Period Sun Jun 8 11:00:00 2008 UTC to Mon Jun 9 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Sun Jun 8 21:01:52 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009675.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Sun Jun 8 21:03:22 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009676.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Sun Jun 8 21:04:52 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009677.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Sun Jun 8 21:06:22 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009678.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Sun Jun 8 21:07:53 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009679.html

1 0

Zope2 porting..module Zope2
by ranjith kannikara 09 Jun '08

09 Jun '08

During the porting of Zope2 to python2.5 We are now porting the module Zope2 which was having 4 failures and 1 error. All of these were due to the change in the hierarchy of exception classes. The failures were arised due to the failure of the function 'SetStatus' in / ** /lib/python/ZPublisher/HTTPResponse.py to set the status. In the above function there is one checking if( isinstance(status, types.ClassType) and issubclass(status, Exception)): status = status.__name__ #status is being set here.. in which status is actually the zException class and it is new style class in python2.5 , therefore this condition always fails and the status is set to arbitrary value 500. We tried removing this first condition ( ie using if(issubclass(status, types.ClassType ) ) and it didn't show any new failures or errors in either python2.4 or 2.5 . And the 4 failures also got vanished. We tried to make out the significance of that first checking but couldn't. What is the significance of this checking ? ( so that the code can be edited to adopt the checking in someother way for python2.5 ) Or Can it be just avoided?

2 1

(no subject)
by Bristow Thankachan 08 Jun '08

08 Jun '08

bristow.thankachan(a)gmail.com

1 0

Zope Tests: 5 OK
by Zope Tests Summarizer 08 Jun '08

08 Jun '08

Summary of messages to the zope-tests list. Period Sat Jun 7 11:00:00 2008 UTC to Sun Jun 8 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Sat Jun 7 21:07:16 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009670.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Sat Jun 7 21:08:46 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009671.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Sat Jun 7 21:10:16 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009672.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Sat Jun 7 21:11:46 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009673.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Sat Jun 7 21:13:16 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009674.html

1 0

buildbot failure in Zope on zc.testbrowser
by ct＠gocept.com 08 Jun '08

08 Jun '08

The Buildbot has detected a new failure of zc.testbrowser on Zope. Full details are available at: http://zopebuildbot.whq.gocept.com/zc.testbrowser/builds/100 Buildbot URL: http://zopebuildbot.whq.gocept.com/ Buildslave for this Build: local Build Reason: The Nightly scheduler named 'zc.testbrowser nightly' triggered this build Build Source Stamp: [branch zc.testbrowser/trunk] HEAD Blamelist: BUILD FAILED: failed test Logs are attached. sincerely, -The Buildbot

2 1