April 2009 - Zope-Dev

Zope Source Code Repository
by Chris Withers 11 Apr '09

11 Apr '09

Hey All, I got bitten by the current zope subversion setup at PyCon so thought I'd mail the appropriate groups about it. If this has been covered elsewhere and I've missed anything, please just point me in the right direction... So, svn.zope.org causes me pain at the moment: - it uses the bizarre svn or svn+ssh protocols, which I find annoying (ports blocked on routers, can't check with a browser, etc) - the web front end is ancient and not as good as other options (Trac, WebSVN) - the process for adding keys is baroque and managed by one person who is too busy to help with it (Jim) So I thought I'd ask what the plans are now that the foundation owns all the Zope IP (has this happened yet or am I imagining things?) Are we sticking with svn? Are we sticking with the current hosting? Are we sticking with the current key-based login and upload mechanism? For me, the ideal would be simply https for everything and using http basic auth for access with more people having access to update the passwd file and maybe Trac or WebSVN for a nice web interface. I volunteer to help with any/all of the above. The other option would be to follow Python and move to Mercurial, but that has the same problems for me as with Bzr (no decent gui tools, less mature, etc) although it's a toolset I'll have to learn at some point anyway... cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

16 56

the notion of a "next" in KGS
by Martijn Faassen 11 Apr '09

11 Apr '09

Hi there, During the post-Pycon sprint Hanno made me aware of a tool called mr.developer. This tool allows you to easily turn a particular package in your buildout into one you want to hack on, without you having to know where to check it out from. mr.developer has a concept of "next" (Plone-next). Given a release of Plone, it needs to find out where the packages live in a version control system, and whether the next version is the trunk or a branch. During the Grok sprint in late january when z3c.recipe.compattest was developed we ran into the same issue. We want to run compattests against some released set of versions, but also against all development versions. We took a shortcut there and just "guess" that all packages in the Zope Framework live on svn.zope.org and are the trunks. This is hardly ideal. During the Pycon sprint Hanno also worked on a buildout recipe to draw dependency graphs: z3c.recipe.depgraph. We want to be able to draw the dependency graph of a selected set of versions, but we also want to be able to draw the dependency graph of all development versions. So we have three tools that need this concept. This implies to me we need to expand the notion of KGS. (where I take it in the broad sense where we are talking about a known good set of something; Zope 2, Zope 3, Zope Framework, Grok, etc). The abstract notion of KGS currently is has these two fields (per package part of the KGS): [pypi package name] [version] If we are to expand this with a "next" notion, it would become like this: [pypi package name] [version] [svn URL] The svn url contains full information about where to check out the next version of the package. If we want to support alternate version control systems, we'd need to expand that, though I hope that all alternate version control systems have a notion of a URL to point to a version. Once we have this extra information, we can publish it. Currently KGS exports the known versions list as a buildout versions section compatible list. We can't put the SVN URL in there. But we could also export another file per KGS release that contained the package name and the SVN URL. I believe mr.developer takes that kind of information. Once we have that, we can then adjust our tools to make use of this extra information. Opinions? People who want to implement this? Regards, Martijn

2 1

uuid.UUID as a rock in zope.security
by Brian Sutherland 11 Apr '09

11 Apr '09

Hi, We're using UUIDs a lot, and it's pretty painful that they are security proxied. They're in the standard library from python 2.5 (http://docs.python.org/library/uuid.html) and are immutable according to the documentation. I think they meet all the all the requirements to be rocks. So unless someone complains, I'll commit the attached patch in a few days. -- Brian Sutherland

8 18

Zope Tests: 8 OK
by Zope Tests Summarizer 11 Apr '09

11 Apr '09

Summary of messages to the zope-tests list. Period Fri Apr 10 12:00:00 2009 UTC to Sat Apr 11 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Tests passed OK --------------- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Fri Apr 10 20:53:29 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011435.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Fri Apr 10 20:55:32 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011436.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Fri Apr 10 20:57:32 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011437.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Fri Apr 10 20:59:32 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011438.html Subject: OK : Zope-trunk Python-2.6.1 : Linux From: Zope Tests Date: Fri Apr 10 21:01:33 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011439.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Fri Apr 10 21:03:33 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011440.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Fri Apr 10 21:05:34 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011441.html Subject: OK : Zope-trunk-alltests Python-2.6.1 : Linux From: Zope Tests Date: Fri Apr 10 21:07:35 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011442.html

1 0

z3c.form and KGS 3.4 - can't build 1.9.x branch
by Martin Aspeli 10 Apr '09

10 Apr '09

Hi, I just tried to check out the new 1.9.x branch of z3c.form (thanks Stephan!), but it won't build with Python 2.4 (I need this to work with Plone, so 2.4 is a must): $ ./bin/buildout Develop: '/users/optilude/Development/Plone/Code/Products/z3c.form/.' Unused options for buildout: 'zope-directory' 'download-directory'. Installing test. Getting distribution for 'z3c.template'. Got z3c.template 1.1a1. Getting distribution for 'z3c.coverage'. Got z3c.coverage 0.1.0. Getting distribution for 'zope.app.container'. Got zope.app.container 3.7.0. Getting distribution for 'zope.security'. Got zope.security 3.6.0. Getting distribution for 'zope.publisher'. Got zope.publisher 3.5.5. Getting distribution for 'zope.pagetemplate'. Got zope.pagetemplate 3.4.1. Getting distribution for 'zope.lifecycleevent'. Got zope.lifecycleevent 3.5.0. Getting distribution for 'zope.configuration'. Got zope.configuration 3.4.1. Getting distribution for 'zope.app.testing'. Got zope.app.testing 3.6.0. Getting distribution for 'zope.app.pagetemplate'. Got zope.app.pagetemplate 3.5.0. Getting distribution for 'ZODB3'. Got ZODB3 3.9.0a12. Getting distribution for 'zope.app.publisher'. Got zope.app.publisher 3.6.0. Getting distribution for 'zope.app.component'. Got zope.app.component 3.6.0. Getting distribution for 'zope.tal'. Got zope.tal 3.5.0. Getting distribution for 'zope.dublincore'. Got zope.dublincore 3.4.2. Getting distribution for 'zope.traversing'. Got zope.traversing 3.5.2. Getting distribution for 'zope.proxy>=3.4.2'. Got zope.proxy 3.5.0. Getting distribution for 'zope.deferredimport'. Got zope.deferredimport 3.5.0. Getting distribution for 'zope.app.security'. Got zope.app.security 3.6.0. Getting distribution for 'zope.app.publication'. Got zope.app.publication 3.5.1. Getting distribution for 'zope.app.authentication'. Got zope.app.authentication 3.5.0a2. Getting distribution for 'zope.app.appsetup>=3.5.0'. Got zope.app.appsetup 3.9.0. Getting distribution for 'zope.contenttype'. Got zope.contenttype 3.4.1. Getting distribution for 'zope.formlib'. Got zope.formlib 3.5.2. Getting distribution for 'zope.filerepresentation'. Got zope.filerepresentation 3.5.0. Getting distribution for 'zope.dottedname'. Got zope.dottedname 3.4.5. Getting distribution for 'zope.app.form'. Got zope.app.form 3.7.1. Getting distribution for 'zope.app.exception'. Got zope.app.exception 3.4.2. Getting distribution for 'zope.app.http'. Got zope.app.http 3.5.0. Getting distribution for 'zope.error'. Got zope.error 3.6.0. Getting distribution for 'zope.session'. Got zope.session 3.8.0. Getting distribution for 'RestrictedPython'. File "build/bdist.macosx-10.3-i386/egg/RestrictedPython/tests/before_and_after25.py", line 30 x.y = y.z if y.z else y.x ^ SyntaxError: invalid syntax File "build/bdist.macosx-10.3-i386/egg/RestrictedPython/tests/before_and_after26.py", line 30 with whatever as x: ^ SyntaxError: invalid syntax File "build/bdist.macosx-10.3-i386/egg/RestrictedPython/tests/security_in_syntax26.py", line 6 with x as _leading_underscore: ^ SyntaxError: invalid syntax File "/Users/optilude/.buildout/eggs/tmpayO5gI/RestrictedPython-3.5.0-py2.4.egg/RestrictedPython/tests/before_and_after25.py", line 30 x.y = y.z if y.z else y.x ^ SyntaxError: invalid syntax File "/Users/optilude/.buildout/eggs/tmpayO5gI/RestrictedPython-3.5.0-py2.4.egg/RestrictedPython/tests/before_and_after26.py", line 30 with whatever as x: ^ SyntaxError: invalid syntax File "/Users/optilude/.buildout/eggs/tmpayO5gI/RestrictedPython-3.5.0-py2.4.egg/RestrictedPython/tests/security_in_syntax26.py", line 6 with x as _leading_underscore: ^ SyntaxError: invalid syntax Got RestrictedPython 3.5.0. Generated script '/users/optilude/Development/Plone/Code/Products/z3c.form/bin/test'. Installing coverage-test. Generated script '/users/optilude/Development/Plone/Code/Products/z3c.form/bin/coverage-test'. Installing coverage-report. Couldn't find index page for 'z3c.coverage' (maybe misspelled?) Generated script '/users/optilude/Development/Plone/Code/Products/z3c.form/bin/coverage-report'. Clearly, I'm getting too new a version of RestrictedPython, but this is running against the 3.4 KGS, so I don't see how that could really happen. :( Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book

3 6

Heads up: Zope Framework -> Zope Toolkit
by Martijn Faassen 10 Apr '09

10 Apr '09

Hi there, The Zope Framework is now renamed to be the "Zope Toolkit". "Framework" proved to be a controversial name that implies a range of things to people we do not want to imply - in particular that you have to buy into the whole in order to use some of its parts. Zope Toolkit is a more neutral name that still implies we manage this as a whole, but doesn't imply you have to buy into the whole in order to use some of the parts. The Zope Toolkit contains a lot of libraries and frameworks, and also an overarching approach to how such frameworks are generally constructed (the component architecture). We now therefore have a Zope Toolkit Steering Group. :) Regards, Martijn

1 0

Zope Tests: 8 OK
by Zope Tests Summarizer 10 Apr '09

10 Apr '09

Summary of messages to the zope-tests list. Period Thu Apr 9 12:00:00 2009 UTC to Fri Apr 10 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Tests passed OK --------------- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Thu Apr 9 20:44:47 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011427.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Thu Apr 9 20:46:49 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011428.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Thu Apr 9 20:48:49 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011429.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Thu Apr 9 20:50:49 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011430.html Subject: OK : Zope-trunk Python-2.6.1 : Linux From: Zope Tests Date: Thu Apr 9 20:52:49 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011431.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Thu Apr 9 20:54:50 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011432.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Thu Apr 9 20:56:53 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011433.html Subject: OK : Zope-trunk-alltests Python-2.6.1 : Linux From: Zope Tests Date: Thu Apr 9 20:58:53 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011434.html

1 0

possible split of zope.app.generations to zope.generations
by Lacko Roman 09 Apr '09

09 Apr '09

Hi, Now when zope refactoring is in progress, would it be possible to refactor zope.app.generations package so there would be for example package zope.generations that would depend only on ZODB3 package ? I'm using zope.app.generations to upgrade the DB schema in my web project, and in future I want to use ZODB3 in my desktop-only projects. Thanks in advance Regards Roman Lacko

3 2

several zope.* libs within gae (was ZCML implementations: where should they go)
by Tobias Rodäbel 09 Apr '09

09 Apr '09

Hi, Shane Hathaway wrote: > Hanno Schlichting wrote: >> Wichert Akkerman wrote: >>> I'ld rather not see a whole slew of extra packagse appear. I also wonder >>> how the extra number of packages and increasing size of sys.path >>> influence performance and restrictions on environments like GAE. >> >> For environments like GAE you don't want setuptools and its magic to be >> part of your application. This is were repackaging your entire app into >> one zipped egg or some other flat structure comes in handy. >> >> Setuptools and eggs are a distribution format from my point of view. >> They are certainly not the best way to deploy your applications. The >> growing sys.path is affecting performance to some degree in all >> deployment environments. > > Well, zc.buildout ought to be able to eliminate this concern for GAE > deployment. I haven't tried the recipe below, but it certainly seems > like the right idea. > > http://pypi.python.org/pypi/rod.recipe.appengine I released a new version today. It's a lot easier now to use several eggs within gae. This test thingy http://zpttest.appspot.com/ uses zope.interface and zope.pagetemplate plus their dependencies. I'm planning to release another sample project maybe during easter holidays. It's much more fun since you zope people cleaned up a lot of dependencies and unveiled zc.buildout. Thanks! Cheers, Tobias

4 3

Why doesn't this buildout run the zdaemon tests?
by Chris Withers 09 Apr '09

09 Apr '09

Hi All, Apologies for the current test failure on trunk, why doesn't the following testrunner run the zdaemon tests? [buildout] parts = test extends = http://svn.zope.org/*checkout*/Zope/tags/2.12.0a1/versions-zope2.cfg versions = versions develop = Zope zdaemon [versions] setuptools = 0.6c9 zc.buildout = 1.2.1 zdaemon = Zope2 = [test] recipe = zc.recipe.testrunner eggs = Zope2 As before, "Zope" contains a checkout of the trunk of the Zope2 egg, and zdaemon contains a checkout of the trunk of zdaemon egg? Zope2 depends on zdaemon, so why are its tests not getting run when I do bin/test? Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

3 4