July 2010 - Zope-Dev

Manuel Beta
by Benji York 14 Jan '11

14 Jan '11

I've just released the first beta of Manuel, my next-generation doctest project. Being that zope-dev has some of the most well-informed users of doctest (and some of the most well-informed non-users of doctest), I'd like to gather feedback from this group before making an announcement to the wider world. Manuel is available from PyPI (http://pypi.python.org/pypi/manuel) with docs, details, and examples at http://packages.python.org/manuel/. I'm interested in any feedback and/or questions you may have be it technical, documentation, or "marketing" (i.e., how do I describe what Manuel does and what benefits it has). -- Benji York Senior Software Engineer Zope Corporation

5 12

zope.dublincore and zope.copypastemove not compatible?
by Michael Howitz 14 Sep '10

14 Sep '10

Hi, I found something strange in metadata when copying a persistent object. My situation is the following: I have a container with some elements inside. I create a copy of this container using zope.copypastemove.ObjectCopier(my_container).copyTo(my_container.__parent__) (Actually I use zope.copypastemove.interfaces.IObjectCopier(my_container) but this calls the adapter mentioned above.) Side note: Is this the right way to copy an persistent object nowadays? This happens tho dublin core metadata then: As zope.dublincore.timeannotators.CreatedAnnotator is subscribed to zope.lifecycleevent.IObjectCreatedEvent it gets called as the ObjectCopiedEvent is a subclass of ObjectCreatedEvent. The copy of the container gets a new creation date set in its metadata. But zope.copypastemove.dispatchToSublocations calls the subscribers for the sublocations using zope.component.subscribers((sub, event), None) So the zope.dublincore.timeannotators.CreatedAnnotator does not get called as it is not registered for (object, event) but only for (event,). This leads to a strange situation: the metadata of the copied container get updated but not the metadata of its contents. This behavior has not changed since version 3.4.0 which was about 2,5 years ago. I think this is a long-standing bug and it should it be fixed in zope.dublincore by registering the subscribers for (object, event)? (Additionally or exclusively, I'm not sure.) Any thoughts? Yours sincerely, -- Michael Howitz · mh(a)gocept.com · software developer gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 8 · fax +49 345 1229889 1 Zope and Plone consulting and development

1 3

Zope 2.12.9 broke ZMySQLDA in the middle of a stable release series
by Leonardo Rochael Almeida 29 Aug '10

29 Aug '10

Hi, The latest Zope 2.12.9 release broke the last release of Products.ZMySQLDA. To demonstrate, bootstrap and run the attached buildout, then run: $ bin/py -c "import Shared.DC.ZRDB, Products.ZMySQLDA" You'll get the following traceback: Traceback (most recent call last): File "bin/py", line 107, in <module> exec _val File "<string>", line 1, in <module> File "/home/leo/opt/zmysqlda/eggs/Products.ZMySQLDA-3.1-py2.6.egg/Products/ZMySQLDA/__init__.py", line 90, in <module> import DA File "/home/leo/opt/zmysqlda/eggs/Products.ZMySQLDA-3.1-py2.6.egg/Products/ZMySQLDA/DA.py", line 243, in <module> os.path.join('Shared','DC','ZRDB','www','DBAdapterFolder_icon.gif'))} File "/home/leo/opt/zmysqlda/eggs/Zope2-2.12.9-py2.6-linux-x86_64.egg/App/ImageFile.py", line 77, in __init__ stat_info = os.stat(path) OSError: [Errno 2] No such file or directory: '/home/leo/opt/zmysqlda/eggs/Zope2-2.12.9-py2.6-linux-x86_64.egg/Shared/DC/ZRDB/www/DBAdapterFolder_icon.gif' Edit buildout.cfg and switch the extends directive to the commented out 2.12.8 tag and see that the above command shows no error, only a deprecation warning that is unrelated to the breakage above. Internal buildbots that tracked the 2.12 branch notified me of this problem, but in between catching up with all the traffic for the mailing lists and the Zope commit, and a day job, I didn't have enough time to track down the issue before the 2.12.9 release was made: there was less than 4 days between spinning off Products.ZSQLMethods and the new 2.12 release. The most trivial fix seems fairly obvious: ZMySQLDA should carry its own icon, but in any case, Zope 2.12 should not break compatibility in the middle of a stable series. I strongly suspect other Zope2 DB adapters to suffer from the same problem. I'm not sure what the proper fix should be. App.ImageFile.ImageFile could grow support for icons outside of software_home, or perhaps the spinning-off of Shared.DC.ZRDB should be delayed to the 2.13 series only, but in any case the 2.12 branch should be a safe upgrade for third party code as much as reasonably possible. suggestions? Cheers, Leo

3 8

Retire zope3-checkins list
by Baiju M 09 Aug '10

09 Aug '10

Hi, What about retiring zope3-checkins list ? Regards, Baiju M

3 3

docs.zope.org automation
by Jens Vagelpohl 04 Aug '10

04 Aug '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, Here's a followup on a docs.zope.org automation task I took over during one of the Zope developer IRC metings[1]. The task was to provide individual package documentation, if it exists, directly underneath docs.zope.org, e.g.: http://docs.zope.org/zope.event/ ... and keep those docs updated from the current trunk documentation. I expanded that task a little bit by generating content that shows the list of packages divided by project and makes it obvious which packages have documentation and which don't. All of that is in a buildout that automatically generates the docs.zope.org website and does away with the single static HTML page with the "dead" new new new new.zope.org design and uses stock Sphinx design. If you visit docs.zope.org now you'll notice that the content on the main page has not changed much, it's just been updated and re-ordered slightly. What's new are those links I prefixed with "Package documentation", those point to the autogenerated index pages for each project. As noted on top of most of these index pages, if a package is listed but not linked it doesn't have documentation the scripts can recognize. Currently the buildout can recognize the standard Sphinx documentation layout with a folder named "doc" or "docs" in the package root and a Sphinx configuration and content therein. The buildout can also use a kludge and pull in content that is documented using "z3c.recipe.sphinxdoc" maintained in a separate buildout, but I'm hoping those project authors would consider using the standard layout as exemplified by e.g. zope.event[2] and championed by e.g. Tres, Christian Theune, and several others (including me). There's a README in the buildout that explains how to do specific tasks[3]. If you have any questions let me know. jens [1] http://docs.zope.org/zopetoolkit/zope-dev/zope-dev-20100727.html [2] http://svn.zope.org/zope.event/trunk/docs/ [3] http://svn.zope.org/docs.zope.org_website/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkxUW7gACgkQRAx5nvEhZLLhAgCgsHQeyHi9/xDc9aYvLELlM1/e Z0sAnirP2CO3zQ/MTntWTixDj7MIStgA =gadb -----END PGP SIGNATURE-----

10 33

Class advisors in Python 3
by Baiju M 02 Aug '10

02 Aug '10

Hi, Does class advisors like 'implements' and 'adapts' are going to work in Python 3 ? If not, should we discourage its usage now ? Regards, Baiju M

6 8

zopectl's -p options
by Chris Withers 31 Jul '10

31 Jul '10

...is currently useless, as far as I can see. This stops you specifying a different location for runzope, which is handy if you're doing buildout-based stuff that uses a deployment. I think the attached patch fixes this, but I'm wondering: - are these are tests for this area - why does self.program need to be a one element list? cheers, Chris =================================================================== --- src/Zope2/Startup/zopectl.py (revision 115104) +++ src/Zope2/Startup/zopectl.py (working copy) @@ -114,11 +114,14 @@ positional_args_allowed = 1 - program = "zopectl" schemadir = os.path.dirname(Zope2.Startup.__file__) schemafile = "zopeschema.xml" uid = gid = None + # this indicates that no explict program has been provided. + # the command line option can set this. + program = None + # XXX Suppress using Zope's <eventlog> section to avoid using the # same logging for zdctl as for the Zope appserver. There still # needs to be a way to set a logfile for zdctl. @@ -169,7 +172,9 @@ config = self.configroot self.directory = config.instancehome self.clienthome = config.clienthome - if config.runner and config.runner.program: + if self.program: + self.program = [self.program] + elif config.runner and config.runner.program: self.program = config.runner.program else: self.program = [os.path.join(self.directory, "bin", "runzope")] -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk

2 3

Zope Tests: 34 OK, 19 Failed, 1 Unknown
by Zope Tests Summarizer 31 Jul '10

31 Jul '10

Summary of messages to the zope-tests list. Period Fri Jul 30 12:00:00 2010 UTC to Sat Jul 31 12:00:00 2010 UTC. There were 54 messages: 6 from Zope Tests, 1 from buildbot at enfoldsystems.com, 4 from buildbot at pov.lt, 13 from buildbot at winbot.zope.org, 19 from ccomb at free.fr, 11 from jdriessen at thehealthagency.com. Test failures ------------- Subject: FAILED : Bluebream / Python2.4.6 32bit linux From: ccomb at free.fr Date: Fri Jul 30 11:39:43 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017565.html Subject: FAILED : Bluebream / Python2.5.2 32bit linux From: ccomb at free.fr Date: Fri Jul 30 11:39:54 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017566.html Subject: FAILED : Bluebream / Python2.6.4 32bit linux From: ccomb at free.fr Date: Fri Jul 30 11:39:56 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017567.html Subject: FAILED : Bluebream / Python2.4.6 32bit linux From: ccomb at free.fr Date: Fri Jul 30 12:23:34 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017569.html Subject: FAILED : Bluebream / Python2.6.4 32bit linux From: ccomb at free.fr Date: Fri Jul 30 12:23:46 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017570.html Subject: FAILED : Bluebream / Python2.5.2 32bit linux From: ccomb at free.fr Date: Fri Jul 30 12:23:50 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017571.html Subject: FAILED : winbot / ztk_dev py_244_win32 From: buildbot at winbot.zope.org Date: Fri Jul 30 22:08:36 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017584.html Subject: FAILED : winbot / ztk_dev py_254_win32 From: buildbot at winbot.zope.org Date: Fri Jul 30 22:15:58 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017586.html Subject: FAILED : winbot / ztk_dev py_265_win32 From: buildbot at winbot.zope.org Date: Fri Jul 30 22:22:51 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017587.html Subject: FAILED : winbot / ztk_dev py_265_win64 From: buildbot at winbot.zope.org Date: Fri Jul 30 22:29:42 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017589.html Subject: FAILED : ZTK 1.0dev / Python2.4.6 Linux 32bit From: ccomb at free.fr Date: Fri Jul 30 23:50:26 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017594.html Subject: FAILED : ZTK 1.0dev / Python2.6.4 Linux 32bit From: ccomb at free.fr Date: Fri Jul 30 23:52:50 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017595.html Subject: FAILED : ZTK 1.0dev / Python2.5.2 Linux 32bit From: ccomb at free.fr Date: Fri Jul 30 23:53:09 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017596.html Subject: FAILED : Zope 3.4.1 KGS / Python2.5.2 32bit linux From: ccomb at free.fr Date: Sat Jul 31 01:28:27 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017600.html Subject: FAILED : winbot / ZODB_dev py_270_win32 From: buildbot at winbot.zope.org Date: Sat Jul 31 03:14:10 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017605.html Subject: FAILED : winbot / ZODB_dev py_270_win64 From: buildbot at winbot.zope.org Date: Sat Jul 31 04:09:46 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017607.html Subject: FAILED : Zope Buildbot / zope2.12 slave-osx From: jdriessen at thehealthagency.com Date: Sat Jul 31 06:56:53 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017608.html Subject: FAILED : Zope Buildbot / zope2 slave-osx From: jdriessen at thehealthagency.com Date: Sat Jul 31 06:57:01 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017609.html Subject: FAILED : Zope Buildbot / ztk slave-osx From: jdriessen at thehealthagency.com Date: Sat Jul 31 06:57:05 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017610.html Unknown ------- Subject: [zodb-tests] buildbot failure in Enfold Systems on zodb-trunk-python-2.6-maestro From: buildbot at enfoldsystems.com Date: Sat Jul 31 04:00:08 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017606.html Tests passed OK --------------- Subject: OK : Zope Buildbot / ztk slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Fri Jul 30 08:00:18 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017564.html Subject: OK : Bluebream / Python2.6.4 32bit linux From: ccomb at free.fr Date: Fri Jul 30 12:14:36 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017568.html Subject: OK : Bluebream / Python2.6.4 32bit linux From: ccomb at free.fr Date: Fri Jul 30 12:28:25 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017572.html Subject: OK : Zope 3.4 Known Good Set / py2.4-64bit-linux From: buildbot at pov.lt Date: Fri Jul 30 21:08:58 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017573.html Subject: OK : Zope 3.4 Known Good Set / py2.4-32bit-linux From: buildbot at pov.lt Date: Fri Jul 30 21:29:12 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017574.html Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Fri Jul 30 21:31:44 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017575.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Fri Jul 30 21:33:44 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017576.html Subject: OK : Zope-2.12 Python-2.6.5 : Linux From: Zope Tests Date: Fri Jul 30 21:35:44 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017577.html Subject: OK : Zope-2.12-alltests Python-2.6.5 : Linux From: Zope Tests Date: Fri Jul 30 21:37:44 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017578.html Subject: OK : Zope-trunk Python-2.6.5 : Linux From: Zope Tests Date: Fri Jul 30 21:39:44 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017579.html Subject: OK : Zope-trunk-alltests Python-2.6.5 : Linux From: Zope Tests Date: Fri Jul 30 21:41:44 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017580.html Subject: OK : Bluebream / Python2.4.6 32bit linux From: ccomb at free.fr Date: Fri Jul 30 22:06:08 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017581.html Subject: OK : Bluebream / Python2.6.4 32bit linux From: ccomb at free.fr Date: Fri Jul 30 22:06:20 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017582.html Subject: OK : Bluebream / Python2.5.2 32bit linux From: ccomb at free.fr Date: Fri Jul 30 22:06:22 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017583.html Subject: OK : Zope 3.4 Known Good Set / py2.5-64bit-linux From: buildbot at pov.lt Date: Fri Jul 30 22:09:20 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017585.html Subject: OK : Zope 3.4 Known Good Set / py2.5-32bit-linux From: buildbot at pov.lt Date: Fri Jul 30 22:29:34 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017588.html Subject: OK : winbot / ztk_10 py_244_win32 From: buildbot at winbot.zope.org Date: Fri Jul 30 22:38:08 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017590.html Subject: OK : winbot / ztk_10 py_254_win32 From: buildbot at winbot.zope.org Date: Fri Jul 30 22:45:52 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017591.html Subject: OK : winbot / ztk_10 py_265_win32 From: buildbot at winbot.zope.org Date: Fri Jul 30 22:53:08 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017592.html Subject: OK : winbot / ztk_10 py_265_win64 From: buildbot at winbot.zope.org Date: Fri Jul 30 23:00:40 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017593.html Subject: OK : winbot / ZODB_dev py_254_win32 From: buildbot at winbot.zope.org Date: Sat Jul 31 00:29:19 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017597.html Subject: OK : Zope 3.4.1 KGS / Python2.4.6 32bit linux From: ccomb at free.fr Date: Sat Jul 31 00:43:29 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017598.html Subject: OK : winbot / ZODB_dev py_265_win32 From: buildbot at winbot.zope.org Date: Sat Jul 31 01:23:44 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017599.html Subject: OK : ZTK 1.0 / Python2.4.6 Linux 32bit From: ccomb at free.fr Date: Sat Jul 31 01:57:32 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017601.html Subject: OK : ZTK 1.0 / Python2.6.4 Linux 32bit From: ccomb at free.fr Date: Sat Jul 31 01:57:54 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017602.html Subject: OK : ZTK 1.0 / Python2.5.2 Linux 32bit From: ccomb at free.fr Date: Sat Jul 31 01:58:35 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017603.html Subject: OK : winbot / ZODB_dev py_265_win64 From: buildbot at winbot.zope.org Date: Sat Jul 31 02:18:40 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017604.html Subject: OK : Zope Buildbot / zope2.12 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Sat Jul 31 07:18:32 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017611.html Subject: OK : Zope Buildbot / zope2 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Sat Jul 31 07:20:27 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017612.html Subject: OK : Zope Buildbot / zope2.12 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Sat Jul 31 07:22:43 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017613.html Subject: OK : Zope Buildbot / zope2 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Sat Jul 31 07:24:43 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017614.html Subject: OK : Zope Buildbot / ztk slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Sat Jul 31 07:25:40 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017615.html Subject: OK : Zope Buildbot / ztk_win slave-win From: jdriessen at thehealthagency.com Date: Sat Jul 31 07:29:20 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017616.html Subject: OK : Zope Buildbot / ztk slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Sat Jul 31 07:30:50 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/017617.html

1 0

Re: [Zope-dev] cAccessControl.so Zope 2.12.7
by Christopher Warner 30 Jul '10

30 Jul '10

This is probably an issue with 2.12.7 to 2.12.10 as current. I haven't tested beyond 2.12.7 however. The AccessControl module; specifically the shared lib cAccessControl.so as built on an osx arch x86_64 is incorrect as the runtime expects i386. In most cases a knowledgable user will able to rebuild this library with something like: gcc -dynamic -bundle -arch i386 > -I/Applications/Plone4/Python-2.6/include/python2.6 > -I/Applications/Plone4/buildout-cache/eggs/ExtensionClass-2.13.1-py2.6-macosx-10.4-i386.egg/ > -I/Applications/Plone4/buildout-cache/eggs/Acquisition-2.13.3-py2.6-macosx-10.4-i386.egg/ > /Applications/Plone4/Python-2.6/lib/libpython2.6.a > /usr/lib/libpython2.6.dylib -L/Applications/Plone4/Python-2.6/lib/ > cAccessControl.c -o cAccessControl.so Unfortunately in the above specific case I'm building against a standalone Plone instance which ships only with a static lib version of Python 2.6. So this doesn't work. This became an issue with Plone 4.0b5 as this is the first version to include Zope 2.12.7 egg. The 2.12.6 egg has the correct arch. The only remedy I can readily see is that however cAccessControl.so is built needs to be built specifically for the i386 arch and stuffed into the egg. -- Christopher Warner http://cwarner.kernelcode.com

2 2

z3c.testsetup test faliure (was Re: Zope Tests: 55 OK, 18 Failed)
by Baiju M 30 Jul '10

30 Jul '10

On Sun, Jul 11, 2010 at 5:49 PM, Christophe Combelles <ccomb(a)free.fr> wrote: > Le 11/07/2010 13:59, Zope Tests Summarizer a écrit : > >> >> Subject: FAILED : Bluebream / Python2.4.6 32bit linux >> From: ccomb at free.fr >> Date: Sat Jul 10 22:05:41 EDT 2010 >> URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016427.html >> >> Subject: FAILED : Bluebream / Python2.5.2 32bit linux >> From: ccomb at free.fr >> Date: Sat Jul 10 22:07:33 EDT 2010 >> URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016428.html >> >> Subject: FAILED : Bluebream / Python2.6.4 32bit linux >> From: ccomb at free.fr >> Date: Sat Jul 10 22:07:34 EDT 2010 >> URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016429.html >> > > This is a failure in z3c.testsetup. Can someone have a look at it? It also fails > with 0.7.0. FYI: In trunk, if I pin zc.recipe.testrunner to 1.2.0, this failure is going away. Regards, Baiju M

4 8