- Zope-Dev - Zope lists

Re: [Zope-dev] z3c.form 2.0
by Wolfgang Schnerring 12 Feb '09

12 Feb '09

* Dan Korostelev <nadako(a)gmail.com> [2009-02-09 19:08]: > Source support - Seems to work fine. I've checked that out in my > sandbox instance with zc.sourcefactory's context-less and > context-based sources. I'd very much like to put in a little bit of flexibility when looking up widgets for source-based fields: zope.formlib looks up the widget for an IChoice field by requiring a multi-adapter for (field, field.source) instead of just the field, thus allowing you to differentiate widgets for different kinds of sources. I'd like to introduce this to z3c.form as well (see attached patch). Would it be alright with you for me to commit this to trunk (to then go into the release)? Wolfgang -- Wolfgang Schnerring · ws(a)gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development

3 3

Where should I update the translation messages?
by Takeshi Yamamoto 11 Feb '09

11 Feb '09

Hello, I would like to update Japanese translation messages of ZMI of Zope 3. I used to do it with launchpad.net but it seems to be gone. Where should I update the translation messages? Regards. Takeshi Yamamoto

3 5

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

11 Feb '09

Summary of messages to the zope-tests list. Period Tue Feb 10 12:00:00 2009 UTC to Wed Feb 11 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: Tue Feb 10 20:58:35 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011080.html Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.7 : Linux From: Zope Tests Date: Tue Feb 10 20:44:00 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011073.html Subject: OK : Zope-2.9 Python-2.4.6 : Linux From: Zope Tests Date: Tue Feb 10 20:46:05 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011074.html Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Tue Feb 10 20:48:05 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011075.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Tue Feb 10 20:50:06 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011076.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Tue Feb 10 20:52:09 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011077.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Tue Feb 10 20:54:09 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011078.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Tue Feb 10 20:56:09 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011079.html

1 0

release of lovely.remotetask?
by Christian Zagrodnick 11 Feb '09

11 Feb '09

Hi, I'd like to create a new release of lovely.remotetask. Could somebody give me (zagy) the pypi rights? Thanks, -- Christian Zagrodnick · cz(a)gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 4 · fax +49 345 1229889 1 Zope and Plone consulting and development

1 0

Lower default socket timeout for buildout?
by Christian Theune 11 Feb '09

11 Feb '09

Hi, in the last week I noticed that reducing buildout's socket timeout to something relatively low (3-5 seconds) made a lot of buildouts go much faster. It looks like various package metadata points off to bad servers that hang. I haven't had a buildout fail on me because of setting such a low timeout -- I only got annoyed when running with the longer default. I wonder whether it might be an idea to lower the default in general? Christian -- Christian Theune · ct(a)gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 7 · fax +49 345 1229889 1 Zope and Plone consulting and development

4 7

ZCML implementations: where should they go
by Martijn Faassen 10 Feb '09

10 Feb '09

Hi there, We've recently had some discussions on where to place the implementation of various ZCML directives. This post is to try to summarize the issue and analyze the options we have. Right now ZCML directives are implemented in packages that contain other implementation. For example, zope.component implements various ZCML directives, and zope.security implements some more. In the case of zope.component, a special [zcml] extras dependency section is declared. If the ZCML dependencies are asked for, using zope.component will suddenly pull in a much larger list of dependencies than the original zope.component dependency list. The ZCML directives are component-related, but do offer extra options that need bits from the wider Zope 3 framework, such as the security infrastructure. In the case of zope.security, this isn't the case. As far as I can see, it doesn't declare any dependency beyond zope.configuration to allow it to implement its ZCML directives. The dependency situation for the ZCML implementations in zope.component doesn't appear ideal. It was therefore proposed to move the ZCML implementations to another package. This could be a new package, or it could be created. Following up on that, it was considered we should move *all* directives from the packages that implement them now into special packages. This would allow some packages to lose the dependency on zope.configuration, which is a relatively minor gain. We have several ways to go: a) continue with the current extra dependencies situation like in zope.component, and in fact clean up other packages that define ZCML to declare ZCML extra dependencies. b) pull out all ZCML implementations from where they are now and put them in special ZCML implementation packages. We could for instance have zcml.component, or zope.component_zcml, or zope.configuration.component. We had a bit of a side-tracked discussion about naming and namespace packages here. c) pull out only those ZCML implementations that cause extra dependencies beyond zope.configuration. So, we extract the bits of zope.component into a new package, but we don't extract bits from zope.security. I personally don't like extras. I think the ideal situation would be if packages had *no* extras at all (even test extras), as it complicates reasoning about the dependency structure. I think with improved structuring of the dependency graph, a package should have enough in its implementation dependencies to implement its tests. We've already experienced some of that last week at the sprint. For ZCML, with improved structuring of the dependency graph a package should only need zope.configuration as an extra package to implement ZCML. For that reason, a) is not really an option for me. That leaves b) and c). I think for now we should go with c), as it's the smallest step forward that will help clean up things. That is, we either find and appropriate package that makes sense for the ZCML implementations in zope.component, or we create a new package. Of course if we create a new package we still have a naming discussion ahead and I risk sparking another naming discussion (as it's easy to have an opinion about names). So, what do people think about option c)? Regards, Martijn

10 21

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

10 Feb '09

Summary of messages to the zope-tests list. Period Mon Feb 9 12:00:00 2009 UTC to Tue Feb 10 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: Mon Feb 9 21:03:04 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011072.html Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.7 : Linux From: Zope Tests Date: Mon Feb 9 20:48:22 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011065.html Subject: OK : Zope-2.9 Python-2.4.6 : Linux From: Zope Tests Date: Mon Feb 9 20:50:26 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011066.html Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Mon Feb 9 20:52:27 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011067.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Mon Feb 9 20:54:27 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011068.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Mon Feb 9 20:56:38 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011069.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Mon Feb 9 20:58:38 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011070.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Mon Feb 9 21:00:40 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011071.html

1 0

Planning for Zope 3.5
by Stephan Richter 10 Feb '09

10 Feb '09

Hi all, now that we have Zope 3.4.0 finally behind us, let's look forward. As I said in the release notes, I am really willing to switch to a 6 months release cycle again. I think there are three areas that we can work on: - Python 2.6 support. I think this should be straight forward. We have to update packages to not use Python 2.6 keywords and review the AST changes. - Dependency reduction. Well, we are in the middle of this work already. - Improve project setup As Shane pointed out, it is hard to get started. The solution could be a combination of documentation and tools, like zopeproject. I am going to setup a Zope 3.5 development KGS shortly. Jim has already created the directory for me on the server. Thoughts? Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. "Zope Stephan Richter"

6 7

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