January 2010 - Zope-Dev

upload zope.app.exception to pypi
by Jan-Wijbrand Kolman 09 Jan '10

09 Jan '10

hello, Would any of the pypi owners of zope.app.exception be so kind to upload the 3.6.0 release to the package index? I see this package has been tagged already a while ago. I think this newer version should also be included in the ZTK versions list, as this version will import the correct ISystemErrorView interface from zope.browser. Thank you in advance. kind regards, jw

3 5

Zope Tests: 6 OK
by Zope Tests Summarizer 08 Jan '10

08 Jan '10

Summary of messages to the zope-tests list. Period Thu Jan 7 12:00:00 2010 UTC to Fri Jan 8 12:00:00 2010 UTC. There were 6 messages: 6 from Zope Tests. Tests passed OK --------------- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Thu Jan 7 20:37:09 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013341.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Thu Jan 7 20:39:09 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013342.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Thu Jan 7 20:41:09 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013343.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Thu Jan 7 20:43:09 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013344.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Thu Jan 7 20:45:09 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013345.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Thu Jan 7 20:47:09 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013346.html

1 0

BlueBream Wave (Online Documentation Collaboration Using Google Wave)
by Baiju M 08 Jan '10

08 Jan '10

Hi All, I started a BlueBream Wave on Google Wave. You are welcome to join. More details are here: http://wiki.zope.org/bluebream/BlueBreamWave This is a wave for collaborating on documentation for BlueBream. I will make this wave public whenever I come online. The invited members can also do the same. Please don't add "easypublic" or any similar bots which makes it permenantly public. You can find the wave by searching "with:public bluebream" in your Google Wave search bar. This weekend I am planning to write some documentation. P.S: This weekend I am not going to my native place (Kerala), so I will be here in Bangalore. Regards, Baiju M

2 2

happy new year
by Roger 07 Jan '10

07 Jan '10

Hi all Since our community is addicted to choose new names for the Zope 3 App Server every half year, why do we not use project names for each release like others do? Anyway, In a migration path point of view we do nothing else then: Zope 3.5 Application Server aka (BlueBream) Release or BlueBream aka (Zope 3 3.5 Application Server) and that's cool. Baiju, keep the good work going on! Regards Roger Ineichen _____________________________ END OF MESSAGE

2 1

Zope Tests: 6 OK
by Zope Tests Summarizer 07 Jan '10

07 Jan '10

Summary of messages to the zope-tests list. Period Wed Jan 6 12:00:00 2010 UTC to Thu Jan 7 12:00:00 2010 UTC. There were 6 messages: 6 from Zope Tests. Tests passed OK --------------- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Wed Jan 6 20:37:22 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013335.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Wed Jan 6 20:39:22 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013336.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Wed Jan 6 20:41:22 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013337.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Wed Jan 6 20:43:22 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013338.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Wed Jan 6 20:45:22 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013339.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Wed Jan 6 20:47:22 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013340.html

1 0

small manuel bugfix
by Chris McDonough 06 Jan '10

06 Jan '10

I added a branch of manuel to the Zope SVN that fixes the codeblock plugin when you use codeblock "roles" such as: .. code-block:: python :linenos: Currently it only works without roles, e.g.: .. code-block:: python The branch is at svn+ssh://svn.zope.org/repos/main/manuel/branches/chrism-codeblocks The diff against the current head is as follows: [chrism@snowpro manuel]$ svn diff =================================================================== --- src/manuel/codeblock.py (.../branches/chrism-codeblocks) (revision 107071) +++ src/manuel/codeblock.py (.../trunk) (revision 107071) @@ -2,9 +2,7 @@ import manuel import textwrap -CODEBLOCK_START = re.compile( - r'(^\.\.\s*(invisible-)?code-block::?\s*python\b(?:\s*\:\w+\:)*)', - re.MULTILINE) +CODEBLOCK_START = re.compile(r'^\.\.\s*(invisible-)?code-block::?\s*python\b', re.MULTILINE) CODEBLOCK_END = re.compile(r'(\n\Z|\n(?=\S))') @@ -15,8 +13,7 @@ def find_code_blocks(document): for region in document.find_regions(CODEBLOCK_START, CODEBLOCK_END): - start_end = CODEBLOCK_START.search(region.source).end() - source = textwrap.dedent(region.source[start_end:]) + source = textwrap.dedent('\n'.join(region.source.splitlines()[1:])) source_location = '%s:%d' % (document.location, region.lineno) code = compile(source, source_location, 'exec', 0, True) document.claim_region(region) I submit it for Benji's consideration.

2 6

Zope Tests: 6 OK
by Zope Tests Summarizer 06 Jan '10

06 Jan '10

Summary of messages to the zope-tests list. Period Tue Jan 5 12:00:00 2010 UTC to Wed Jan 6 12:00:00 2010 UTC. There were 6 messages: 6 from Zope Tests. Tests passed OK --------------- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Tue Jan 5 20:37:03 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013329.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Tue Jan 5 20:39:03 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013330.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Tue Jan 5 20:41:03 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013331.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Tue Jan 5 20:43:04 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013332.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Tue Jan 5 20:45:04 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013333.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Tue Jan 5 20:47:04 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013334.html

1 0

Where best to intercept a request to send a 304 response in Zope 2
by Martin Aspeli 06 Jan '10

06 Jan '10

Hi, A few of us are playing with some caching tools, trying to get to a more sane and less monkey patch-laden approach than CacheFu (Products.CacheSetup), for use with Zope 2.12. It is relatively easy to set response headers, e.g. in an IPubBeforeCommit event handler. However, we also need to be able to intercept a request to send a 304 response if the underlying object has not been modified. CacheFu monkey patches ZPT rendering to avoid the actual rendering if a 304 response is being sent, returning an empty string instead. I'd rather not have such patches, though, and anyway this only work with things rendered as ZPTs. It also doesn't avoid any pre-work that a view may do before rendering its template, if indeed it has one. Another thought was to use IPubAfterTraversal, at which point we have the object to publish and security checks have been completed. However, ZPublisher.Publish goes straight from that into mapply(). Can anyone think of a good way to do this? Maybe we need to add some kind of condition around mapply(), e.g. to do not nothing if there's a 304 response header, or some other marker? Cheers, Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book

3 4

zope.publisher 3.12 broke 25 zope.app packages
by Martijn Faassen 06 Jan '10

06 Jan '10

Hi there, 25 zope.app packages are broken due to changes in zope.publisher 3.12. zope.publisher had some components factored out of it into zope.login. I fixed zope.app.exception: it could be fixed by adding the zope.login requirement and adding a zcml include statement. I suspect most, probably all, other failures are similarly shallow. The breaking of so many packages wasn't noticed by anyone, until tests of svn checkouts that previously worked now broke. I hope we can put mechanisms in place so that developers of ZTK packages can be better made aware of breaking other packages that depend on the ZTK. This way the developer making the changes could do one or more of the following: * provide better backward compatibility * fix up the breaking packages * provide a better warning to others who are maintaining these packages that something was broken. I faintly, faintly recall we had such early-warning mechanisms in the past. :) Regards, Martijn

4 5

new zope.schema and zope.configuration releases
by Chris McDonough 06 Jan '10

06 Jan '10

FYI, I just made two new releases: zope.schema 3.6.1 zope.configuration 3.7.1 These releases provide basic compatibility with Jython. - C

2 1