[Zope-dev] Re: [Zope-CMF] CMF Tests: 9 OK, 2 Unknown
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Subject: UNKNOWN : CMF-2.1 Zope-trunk Python-2.4.4 : Linux From: CMF Unit Tests Date: Sun Mar 11 22:42:15 EDT 2007 URL: http://mail.zope.org/pipermail/cmf-tests/2007-March/004319.html Subject: UNKNOWN : CMF-trunk Zope-trunk Python-2.4.4 : Linux From: CMF Unit Tests Date: Sun Mar 11 22:45:16 EDT 2007 URL: http://mail.zope.org/pipermail/cmf-tests/2007-March/004321.html I've taken a quick look at the cause of failure, which is the testrunner module in /lib/python/zope/testing/testrunner.py. I compared it to the code on the Zope 2.10 branch and to my untrained eye it looks like some patches applied to the 2.10 branch have not been ported to the zope.testing package used on the Zope 2 trunk. These svn log entries from the Zope 2.10 testrunner.py module look like candidates: - r68925 | Zen | 2006-06-30 13:49:37 +0200 (Fri, 30 Jun 2006) | 3 lines Fix ordering of testSetUp and testTearDown calls, and allow new style classes to be used as Layers by explicitly ignoring the object baseclass. - r68745 | Zen | 2006-06-19 08:55:27 +0200 (Mon, 19 Jun 2006) | 1 line Merged /zope.testing/branches/stub-testSetUp_in_layer 68684:68744 I'm not exactly sure how to proceed, maybe the patch author can comment? jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFF9UN7RAx5nvEhZLIRApL3AJ0cX2A6tS0g3VakOoQnRYreaMFSJwCfdt2r 2LkEjCeJEhunZb/D2fIgzjs= =7UlC -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Zope Tests: 5 OK
Summary of messages to the zope-tests list. Period Sun Mar 11 12:00:00 2007 UTC to Mon Mar 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: Sun Mar 11 21:58:04 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-March/007433.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Sun Mar 11 21:59:34 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-March/007434.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Sun Mar 11 22:01:04 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-March/007435.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Sun Mar 11 22:02:34 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-March/007436.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Sun Mar 11 22:04:04 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-March/007437.html ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Upcoming Zope releases (fwd)
Please stay on the list! Bugs that are not reported through the bugtracker don't exist by definition :-) So the answer is: no. -aj Forwarded Message Date: 12. März 2007 12:16:15 +0100 From: "M. Krainer" <[EMAIL PROTECTED]> To: Andreas Jung <[EMAIL PROTECTED]> Subject: Re: [Zope-dev] Upcoming Zope releases On 3/10/07, Andreas Jung <[EMAIL PROTECTED]> wrote: Hi, I plan to release in about two weeks: - Zope 2.8.9 Will 2.8.9 include a fix for the problem with the zeo server conflict resolution? For details and solution please see: http://mail.zope.org/pipermail/zope-dev/2006-June/027573.html http://mail.zope.org/pipermail/zope-dev/2006-June/027583.html -- Markus -- End Forwarded Message -- -- ZOPYX Ltd. & Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany Web: www.zopyx.com - Email: [EMAIL PROTECTED] - Phone +49 - 7071 - 793376 Registergericht: Amtsgericht Stuttgart, Handelsregister A 381535 Geschäftsführer/Gesellschafter: ZOPYX Limited, Birmingham, UK E-Publishing, Python, Zope & Plone development, Consulting pgpAhNcbdsM4S.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Views on catalog results
Hi all, This weekend I had fun with creating views for catalog results. In order to do this, I had to: - Create an ICatalogResult interface and use a five:implements directive to configure ZCatalog.CatalogBrains.AbstractCatalogBrain as implementing it. - Set Five.traversable.Traversable as a mixin brain for catalog results (Catalog.useBrains). With these changes, I could a) define views for catalog result objects, and b) traverse over them in a template to obtain the view. I'd like to add this to Zope trunk, with Traversable a base class for AbstractCatalogBrain and a implements(ICatalogResult) on that same class. The obvious advantage of the latter is that one doesn't need to use Catalog.useBrains any more to add functionality to result objects (just use adapters). The first change is a necessity if you want to be able to look up views on results through traversal (in a template for example). I'd like to have some feedback on this idea before I do this however, just to make sure that using Traversable here is a good idea or not. For the curious, my usecase involved creating workflow menus (a lá Plone) for a page showing up to 100s of content objects, all AJAX driven. This enables you to quickly workflow several related objects without waking up all the content objects just to see their available workflow transitions. The workflow actions menu is a view defined for both content objects and catalog results, with the view also supporting invoking the transition. There are different view classes for content objects and catalog results, but the template for the view is the same for both cases. The catalog result view looks up transitions by hacking up action information objects, and the only limitation is that transition guards can not use permission or roles guards (no meaningful context to look up on) and guard expressions need to be written taking into account that the context is either a real content object or a catalog result. These limitations were not a problem for the workflows involved. -- Martijn Pieters ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
