February 2009 - Zope-Dev

Tests results for Zope 3.5dev KGS
by Stephan Richter 09 Feb '09

09 Feb '09

Hi all, I just ran all tests over night and here is the result Tests with errors: runTest (zope.testing.testrunner.runner.SetUpLayerFailure) runTest (zope.testing.testrunner.runner.SetUpLayerFailure) runTest (zope.testing.testrunner.runner.SetUpLayerFailure) runTest (zope.testing.testrunner.runner.SetUpLayerFailure) runTest (zope.testing.testrunner.runner.SetUpLayerFailure) runTest (zope.testing.testrunner.runner.SetUpLayerFailure) testDoomedTransaction (zope.app.publication.tests.test_zopepublication.ZopePublicationTests) testTransactionAnnotation (zope.app.publication.tests.test_zopepublication.ZopePublicationTests) testTransactionCommitAfterCall (zope.app.publication.tests.test_zopepublication.ZopePublicationTests) testAbortTransactionWithErrorReportingUtility (zope.app.publication.tests.test_zopepublication.ZopePublicationErrorHandling) Tests with failures: /opt/zope/packages/eggs/ZODB3-3.9.0a10-py2.5-linux-i686.egg/ZEO/tests/zeo_blob_cache.test /opt/zope/packages/eggs/z3c.etestbrowser-1.2.1-py2.5.egg/z3c/etestbrowser/README.txt /opt/zope/packages/eggs/z3c.layer.minimal-1.0.1-py2.5.egg/z3c/layer/minimal/tests/../README.txt /opt/zope/packages/eggs/zope.app.testing-3.6.0-py2.5.egg/zope/app/testing/cookieTestOne.txt /opt/zope/packages/eggs/zope.app.testing-3.6.0-py2.5.egg/zope/app/testing/cookieTestTwo.txt /opt/zope/packages/eggs/zope.file-0.4.0-py2.5.egg/zope/file/contenttype.txt /opt/zope/packages/eggs/zope.file-0.4.0-py2.5.egg/zope/file/download.txt /opt/zope/packages/eggs/zope.file-0.4.0-py2.5.egg/zope/file/upload.txt /opt/zope/packages/eggs/zope.html-1.1.0-py2.5.egg/zope/html/browser.txt /opt/zope/packages/eggs/z3c.form-1.9.0-py2.5.egg/z3c/form/tests/../form.txt /opt/zope/packages/eggs/z3c.form-1.9.0-py2.5.egg/z3c/form/tests/../group.txt /opt/zope/packages/eggs/z3c.formjs-0.4.1-py2.5.egg/z3c/formjs/tests/../jsclientevent.txt /opt/zope/packages/eggs/zc.catalog-1.3.0-py2.5.egg/zc/catalog/extentcatalog.txt /opt/zope/packages/eggs/zc.catalog-1.3.0-py2.5.egg/zc/catalog/extentcatalog.txt normalize (zc.i18n.date) /opt/zope/packages/eggs/zc.table-0.7.0-py2.5.egg/zc/table/column.txt /opt/zope/packages/eggs/zc.table-0.7.0-py2.5.egg/zc/table/fieldcolumn.txt test_ctl (zc.zope3recipes.tests) test_sane_errors_from_recipe (zc.zope3recipes.tests) work_with_old_zc_deployment (zc.zope3recipes.tests) /opt/zope/packages/eggs/zc.zope3recipes-0.7.0-py2.5.egg/zc/zope3recipes/README.txt test_provides (zope.app.interface.tests.test_interface.PersistentInterfaceTest) test_error_handling (zope.formlib.tests) /opt/zope/packages/eggs/zope.schema-3.5.1-py2.5.egg/zope/schema/tests/../validation.txt /opt/zope/packages/eggs/zope.testing-3.7.1-py2.5.egg/zope/testing/setupstack.txt /opt/zope/packages/eggs/zope.testing-3.7.1-py2.5.egg/zope/testing/testrunner/testrunner-debugging-layer-setup.test /opt/zope/packages/eggs/zope.testing-3.7.1-py2.5.egg/zope/testing/testrunner/testrunner-layers-ntd.txt /opt/zope/packages/eggs/zope.testing-3.7.1-py2.5.egg/zope/testing/testrunner/testrunner-layers.txt /opt/zope/packages/eggs/zope.testing-3.7.1-py2.5.egg/zope/testing/testrunner/testrunner-profiling.txt /opt/zope/packages/eggs/zope.testing-3.7.1-py2.5.egg/zope/testing/testrunner/testrunner-profiling-cprofiler.txt Total: 12937 tests, 30 failures, 10 errors in 41 minutes 1.150 seconds. Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. "Zope Stephan Richter"

4 10

zope.security changes
by Martijn Faassen 09 Feb '09

09 Feb '09

Hi there, In the dependency cleanup effort we've got going on at the Grok cavesprint here at my house, we have moved code around some more. zope.security was already defining ZCML directives so we've moved the <class> directive from zope.app.component and and the <module> directive from zope.app.security into zope.security as well. These only need things that are in zope.security already (or its dependencies) and the directives are about security declarations, so they seem to fit quite well into their new place. This way we can (eventually) lift some dependencies of packages on zope.app.security and zope.app.component and point it to zope.security instead, which will help clean up the dependency structures. We've left backwards compatibility imports in place in the zope.app.* packages (hopefully enough of it) so that existing code will continue to work. Regards, Martijn

12 28

Zope Tests: 7 OK, 1 Failed
by Zope Tests Summarizer 09 Feb '09

09 Feb '09

Summary of messages to the zope-tests list. Period Sun Feb 8 12:00:00 2009 UTC to Mon Feb 9 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Test failures ------------- Subject: FAILED (failures=1) : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Sun Feb 8 21:01:53 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011064.html Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.7 : Linux From: Zope Tests Date: Sun Feb 8 20:47:39 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011057.html Subject: OK : Zope-2.9 Python-2.4.5 : Linux From: Zope Tests Date: Sun Feb 8 20:49:42 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011058.html Subject: OK : Zope-2.10 Python-2.4.5 : Linux From: Zope Tests Date: Sun Feb 8 20:51:42 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011059.html Subject: OK : Zope-2.11 Python-2.4.5 : Linux From: Zope Tests Date: Sun Feb 8 20:53:43 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011060.html Subject: OK : Zope-trunk Python-2.4.5 : Linux From: Zope Tests Date: Sun Feb 8 20:55:47 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011061.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Sun Feb 8 20:57:48 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011062.html Subject: OK : Zope-trunk-alltests Python-2.4.5 : Linux From: Zope Tests Date: Sun Feb 8 20:59:49 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011063.html

1 0

Re: [Zope-dev] [Checkins] SVN: z3c.layer/tags/0.3.0/setup.py -dev
by Michael Howitz 09 Feb '09

09 Feb '09

Am 08.02.2009 um 05:14 schrieb Stephan Richter: > On Saturday 07 February 2009, Michael Howitz wrote: >> Changed: >> U z3c.layer/tags/0.3.0/setup.py > > I'll note that we retired this package in favor of > > z3c.layer.minimal > z3c.layer.trusted > etc. Thanks for clarification. After releasing z3c.layer I noticed the other packages. So I'll do another release pointing to the split-of packages and delete the trunk of z3c.layer so it is clear that the package is dead. 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 0

zope.location.pickling.PathPersistent
by Dan Korostelev 08 Feb '09

08 Feb '09

Hi there. While refactoring zope.location to use the new zope.copy package, I came on PathPersistent class in the zope.location.pickling module. It does quite the same as old CopyPersistent, but based on object location paths instead of ids. I can't find any code that actually uses that class and I don't think that it makes much sense. So I'd propose to just remove it. What do you people think? Also, Martijn, Christian, was it the only reason for moving ITraverser interface from zope.traversing to zope.location? If so, can we still move it back? -- WBR, Dan Korostelev

1 0

Merge zc.copy with zope.copypastemove and zope.location.
by Dan Korostelev 08 Feb '09

08 Feb '09

The README.txt of zc.copy says that the components, provided by this package is apropriate for inclusion in Zope itself. The package provides a more pluggable mechanism for copying generic persistent objects (not only ILocation's) as well as a way to register post-copy hooks to be executed, which is very useful, for example when dealing with persistent objects that have non-ZODB bits (like filesystem based files related and so on). However, the package is really small and mostly contains modified copies of zope.copypastemove's ObjectCopier and zope.location's locationCopy. So, I propose to merge the zc.copy package's changes with original zope.copypastemove/zope.location and deprecate it. If noone objects, I'll do that myself. -- WBR, Dan Korostelev

2 5

Zope Tests: 6 OK, 4 Failed
by Zope Tests Summarizer 08 Feb '09

08 Feb '09

Summary of messages to the zope-tests list. Period Sat Feb 7 12:00:00 2009 UTC to Sun Feb 8 12:00:00 2009 UTC. There were 10 messages: 10 from Zope Tests. Test failures ------------- Subject: FAILED (failures=6) : Zope-trunk Python-2.4.5 : Linux From: Zope Tests Date: Sat Feb 7 21:10:33 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011051.html Subject: FAILED (failures=7) : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Sat Feb 7 21:12:03 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011052.html Subject: FAILED (failures=6) : Zope[2.buildout]-trunk-alltests Python-2.4.5 : Linux From: Zope Tests Date: Sat Feb 7 21:16:35 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011055.html Subject: FAILED (failures=7) : Zope[2.buildout]-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Sat Feb 7 21:18:05 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011056.html Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.7 : Linux From: Zope Tests Date: Sat Feb 7 21:04:32 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011047.html Subject: OK : Zope-2.9 Python-2.4.5 : Linux From: Zope Tests Date: Sat Feb 7 21:06:02 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011048.html Subject: OK : Zope-2.10 Python-2.4.5 : Linux From: Zope Tests Date: Sat Feb 7 21:07:32 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011049.html Subject: OK : Zope-2.11 Python-2.4.5 : Linux From: Zope Tests Date: Sat Feb 7 21:09:02 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011050.html Subject: OK : Zope[2.buildout]-trunk Python-2.4.5 : Linux From: Zope Tests Date: Sat Feb 7 21:13:33 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011053.html Subject: OK : Zope[2.buildout]-trunk Python-2.5.4 : Linux From: Zope Tests Date: Sat Feb 7 21:15:03 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011054.html

1 0

Zope Tests: 6 OK, 4 Failed
by Zope Tests Summarizer 07 Feb '09

07 Feb '09

Summary of messages to the zope-tests list. Period Fri Feb 6 12:00:00 2009 UTC to Sat Feb 7 12:00:00 2009 UTC. There were 10 messages: 10 from Zope Tests. Test failures ------------- Subject: FAILED (failures=6) : Zope-trunk Python-2.4.5 : Linux From: Zope Tests Date: Fri Feb 6 21:19:46 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011041.html Subject: FAILED (failures=7) : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Fri Feb 6 21:21:19 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011042.html Subject: FAILED (failures=6) : Zope[2.buildout]-trunk-alltests Python-2.4.5 : Linux From: Zope Tests Date: Fri Feb 6 21:26:03 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011045.html Subject: FAILED (failures=7) : Zope[2.buildout]-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Fri Feb 6 21:27:33 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011046.html Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.7 : Linux From: Zope Tests Date: Fri Feb 6 21:13:43 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011037.html Subject: OK : Zope-2.9 Python-2.4.5 : Linux From: Zope Tests Date: Fri Feb 6 21:15:14 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011038.html Subject: OK : Zope-2.10 Python-2.4.5 : Linux From: Zope Tests Date: Fri Feb 6 21:16:46 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011039.html Subject: OK : Zope-2.11 Python-2.4.5 : Linux From: Zope Tests Date: Fri Feb 6 21:18:16 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011040.html Subject: OK : Zope[2.buildout]-trunk Python-2.4.5 : Linux From: Zope Tests Date: Fri Feb 6 21:22:49 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011043.html Subject: OK : Zope[2.buildout]-trunk Python-2.5.4 : Linux From: Zope Tests Date: Fri Feb 6 21:24:33 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011044.html

1 0

Re: [Zope-dev] SVN: zope.app.component/trunk/ Please, don't just remove things that could be used in users code.
by Martijn Faassen 06 Feb '09

06 Feb '09

Dan Korostelev wrote: > Log message for revision 96156: > Please, don't just remove things that could be used in users code. > > Changed: > U zope.app.component/trunk/CHANGES.txt > U zope.app.component/trunk/src/zope/app/component/metadirectives.py > > -=- > Modified: zope.app.component/trunk/CHANGES.txt > =================================================================== > --- zope.app.component/trunk/CHANGES.txt 2009-02-05 18:07:51 UTC (rev 96155) > +++ zope.app.component/trunk/CHANGES.txt 2009-02-05 18:22:19 UTC (rev 96156) > @@ -5,7 +5,9 @@ > 3.6.1 (unreleased) > ------------------ > > -- ... > +- Make ``class`` directive schemas importable from old location, > + raising a deprecation warning. It was moved in the previous release, > + but some custom directives could possibly use its schemas. Out of curiosity, *was* it used by custom directives that you know of? A more philosophical question: are the interfaces used to implement a directive part of a public API that is reusable or not? When we moved the directive implementation I arbitrary made the assumption that it'd be fine to just move them wholesale, but you clearly don't agree. Besides the interfaces, should the implementation also have backwards compatibility imports? I guess sometimes reuse by interface subclassing does happen in directive implementation, but of course we could declare that such reuse is only intra-package. In my mind, it's also less risky to move a directive implementation even if it is reused, as the amount of external reuse is likely rare and is less likely to be in end-user code. The developers of the code layered on top of the directive definition would therefore be quite capable of fixing any breakage quickly. But of course placing a few imports for backwards compatibility is not a lot of work and may be the easiest way out of this set of questions. :) Regards, Martijn

4 7

Important release migration information
by Dan Korostelev 06 Feb '09

06 Feb '09

I just committed a new section to zope3docs about migration to newer Zope 3 releases. I think we should maintain a list of most important changes that could break backward-compatibility, like recent changing exception types used in zope.container in a separate document, so people who are upgrading from, say, Zope 3.4 to Zope 3.5 could easily find the bits about problems that can pop up in the transition. What are you thinking about that? -- WBR, Dan Korostelev

2 3