June 2007 - Zope-Dev

Zope Tests: 5 OK
by Zope Tests Summarizer 14 Jun '07

14 Jun '07

Summary of messages to the zope-tests list. Period Wed Jun 13 12:00:00 2007 UTC to Thu Jun 14 12:00:00 2007 UTC. There were 5 messages: 5 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Wed Jun 13 20:52:25 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-June/007879.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Wed Jun 13 20:53:55 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-June/007880.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Wed Jun 13 20:55:26 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-June/007881.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Wed Jun 13 20:56:58 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-June/007882.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Wed Jun 13 20:58:29 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-June/007883.html

1 0

Zope Tests: 5 OK
by Zope Tests Summarizer 13 Jun '07

13 Jun '07

Summary of messages to the zope-tests list. Period Tue Jun 12 12:00:00 2007 UTC to Wed Jun 13 12:00:00 2007 UTC. There were 5 messages: 5 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Tue Jun 12 20:52:38 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-June/007874.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Tue Jun 12 20:54:09 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-June/007875.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Tue Jun 12 20:55:40 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-June/007876.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Tue Jun 12 20:57:12 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-June/007877.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Tue Jun 12 20:58:47 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-June/007878.html

1 0

Zope Tests: 5 OK
by Zope Tests Summarizer 12 Jun '07

12 Jun '07

Summary of messages to the zope-tests list. Period Mon Jun 11 12:00:00 2007 UTC to Tue Jun 12 12:00:00 2007 UTC. There were 5 messages: 5 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Mon Jun 11 20:51:44 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-June/007869.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Mon Jun 11 20:53:17 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-June/007870.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Mon Jun 11 20:54:48 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-June/007871.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Mon Jun 11 20:56:25 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-June/007872.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Mon Jun 11 20:57:59 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-June/007873.html

1 0

Testing zope 3 utilities from zope 2
by David Convent 12 Jun '07

12 Jun '07

hi, I'm writing a unit test for GS exportimport of the Plone 3.0 plone.app.viewletmanager product. the exportimport handler configures a storage which is a Zope 3 utility. As I want to include support for same node attributes than the skins tool exportimport handler, I took inspiration from the tests in CMFCore/exportimport/tests. My problem is that the utility keeps its settings in all test methods of a test case. Therefore, I can not properly test the exportimport steps. I tried to call unregisterUtility() in the tearDown() method of the test class but that doesn't change anything. Any suggesion on how to solve this particular problem? Current state of the code is in https://svn.plone.org/svn/plone/plone.app.viewletmanager/branches/6649-defa… the test_z_means_last() test method output make it obvious, the utility keeps its settings. Thank you in advance, David

1 1

Zope Tests: 5 OK
by Zope Tests Summarizer 11 Jun '07

11 Jun '07

Summary of messages to the zope-tests list. Period Sun Jun 10 12:00:00 2007 UTC to Mon Jun 11 12:00:00 2007 UTC. There were 5 messages: 5 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Sun Jun 10 20:49:13 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-June/007864.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Sun Jun 10 20:50:45 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-June/007865.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Sun Jun 10 20:52:16 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-June/007866.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Sun Jun 10 20:53:47 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-June/007867.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Sun Jun 10 20:55:18 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-June/007868.html

1 0

Zope2 and eggs
by Wichert Akkerman 10 Jun '07

10 Jun '07

I wanted to share a bit of experience I just had with use of eggs in Zope2. For a project I am working on I want to use the zope.sendmail package in a Zope2 environment managed using buildout. I added zope.sendmail to the eggs list in the buildout configuration and ran buildout. This pulled in a large part of the Zope3 packages. This produced conflicts between those packages and the ones included in Zope2 which resulted in a pretty boken instance: [snow;..stances/revelation]-84> bin/instance test -s zope.sendmail Traceback (most recent call last): File "bin/instance", line 205, in ? plone.recipe.zope2instance.ctl.main( File "/local/buildout/eggs/plone.recipe.zope2instance-0.3-py2.4.egg/plone/recipe/zope2instance/ctl.py", line 154, in main c = AdjustedZopeCmd(options) File "/local/buildout/eggs/tmpCiQPa8/zdaemon-2.0a6-py2.4.egg/zdaemon/zdctl.py", line 141, in __init__ AttributeError: 'dict' object has no attribute 'mapping' Adding zope.sendmail as a develop egg instead of a normal egg worked fine though; no zope.* packages were pulled in by buildout and the zope.sendmail unittests run flawlessly. Wichert. -- Wichert Akkerman <wichert(a)wiggy.net> It is simple to make things. http://www.wiggy.net/ It is hard to make things simple.

4 7

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

10 Jun '07

Summary of messages to the zope-tests list. Period Sat Jun 9 12:00:00 2007 UTC to Sun Jun 10 12:00:00 2007 UTC. There were 5 messages: 5 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Sat Jun 9 20:50:41 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-June/007859.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Sat Jun 9 20:52:12 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-June/007860.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Sat Jun 9 20:53:43 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-June/007861.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Sat Jun 9 20:55:14 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-June/007862.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Sat Jun 9 20:56:44 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-June/007863.html

1 0

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

09 Jun '07

Summary of messages to the zope-tests list. Period Fri Jun 8 12:00:00 2007 UTC to Sat Jun 9 12:00:00 2007 UTC. There were 5 messages: 5 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Fri Jun 8 20:52:50 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-June/007854.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Fri Jun 8 20:54:22 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-June/007855.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Fri Jun 8 20:55:54 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-June/007856.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Fri Jun 8 20:57:24 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-June/007857.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Fri Jun 8 20:58:56 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-June/007858.html

1 0

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

08 Jun '07

Summary of messages to the zope-tests list. Period Thu Jun 7 12:00:00 2007 UTC to Fri Jun 8 12:00:00 2007 UTC. There were 5 messages: 5 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Thu Jun 7 20:50:03 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-June/007849.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Thu Jun 7 20:51:34 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-June/007850.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Thu Jun 7 20:53:05 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-June/007851.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Thu Jun 7 20:54:35 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-June/007852.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Thu Jun 7 20:56:06 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-June/007853.html

1 0

shipping with standard docutils
by Philipp von Weitershausen 07 Jun '07

07 Jun '07

At the PIKTipi sprint this past weekend, Andi Zeidler, Andreas Jung and I worked on integrating ZODB 3.8 and Zope 3.4 into the Zope 2 trunk. Zope 3.4 has actually "exploded" into many eggs that are now independently managed and released. I therefore looked into a way to make Zope 2 dependent on these eggs instead of shipping with its own copies of the packages. There are clear benefits to that: * as newer versions of specific zope.* or ZODB packages are released, you can individually install those or not. There'll be no need to wait for another Zope 2 release. * many third-party packages that we had to ship with Zope 2 were actually dependencies of the included Zope 3 (pytz, ClientForm, etc.). The Zope 3 eggs now simply depend on them via the egg dependency mechanism, which means we no longer have to track those projects through vendor imports. * I actually went a bit further and eggified Zope 2 (it seemed the logical conclusion). I didn't really explode Zope 2, it's one big egg (except for a few things that are completely independent, such as ExtensionClass, Acquisition, DateTime, zLOG). Though currently not very comfortable to use, the Zope2 egg seems fully functional and I see it as a (if not *the*) way to distribute Zope 2 in the future. Coming to the actual problem: docutils is one third-party dependency of Zope that we track as a vendor import. Due to certain security problems that can arise when rendering reStructuredText, the docutils code was patched. Therefore, when shipping Zope with the standard docutils distribution (which can be conveniently pulled down as an egg), tests that assert the security of reStructuredText obviously fail. Andi converted the patch that was done to docutils to a monkey patch. It's available on the 'witsch-zope2.11-with-standard-docutils' branch. Not only am I not a big fan of monkey patches, I also think the behaviour of failing with an exception instead of presenting a warning is not very friendly. Tres explained the reason for patching docutils to raise a NotImplementedError in an email message on 8 July 2006: > In Zope2 land, the module is still available, and can be used by other > code (which may not know of that issue). I'm *not* in favor of shipping > an un-patched docutils until we work this out. For instance, perhaps we > should be patching docutils to make the *default* settings disable file > inclusion and 'raw'; then the trusted code which wanted to render reST > which legitimately needed those features could enable them explicitly. In my 'philikon-zope2.11-with-standard-docutils' branch, I have done that "working out": making all reStructuredText rendering from Zope immune to 'include' and 'raw' directives. Instead of raising a NotImplementedError, however, I simply changed the default settings in docutils (via monkey patch that's much less intrusive than swapping out methods). I propose to merge my branch to the trunk, therefore effectively changing the way we deal with the forbidden 'include' and 'raw' directives (presenting warning, not raising NotImplementedError), and allowing us to work with a standard docutils distribution. If wanted, I'd also be willing to backport this to older Zopes, though that might change their behaviour regarding reStructuredText in an unwanted way within a bugfix release. -- http://worldcookery.com -- Professional Zope documentation and training

3 4