- Zope-Dev - Zope lists

Re: [Zope-dev] [Zope3-checkins] [Checkins] SVN: zope.app.component/trunk/setup.py set missing minimum version
by Wichert Akkerman 12 Apr '09

12 Apr '09

Previously Stephan Richter wrote: > On Saturday 14 March 2009, Michael Howitz wrote: > > Log message for revision 98113: > > set missing minimum version > > > > > > Changed: > > U zope.app.component/trunk/setup.py > > > > -=- > > Modified: zope.app.component/trunk/setup.py > > =================================================================== > > --- zope.app.component/trunk/setup.py 2009-03-14 19:56:47 UTC (rev 98112) > > +++ zope.app.component/trunk/setup.py 2009-03-14 20:14:47 UTC (rev 98113) > > @@ -78,7 +78,7 @@ > > 'zope.interface', > > 'zope.lifecycleevent', > > 'zope.location>3.4.0b1', > > - 'zope.publisher', > > + 'zope.publisher>=3.6.0', > > 'zope.schema', > > 'zope.security', > > 'zope.traversing', > > Please, please, please no versions in setup.py. If the package does not work with an older version of zope.publisher than imho that version restriction *has* to be in setup.py. Wichert. -- Wichert Akkerman <wichert(a)wiggy.net> It is simple to make things. http://www.wiggy.net/ It is hard to make things simple.

16 62

naming Zope
by Martijn Faassen 12 Apr '09

12 Apr '09

Hi there, There was some discussion recently on how to name Zope in the future. Here are my thoughts and suggestions. First of all some principles I tend to follow surrounding names. * I prefer not introducing too many new names at the same time. A renaming takes a while to percolate through the community and people to gain full understanding of it. * I prefer naming something that already exists (or renaming something) as opposed to naming something that doesn't really exist yet. A name is a handle on something that we can then use to talk about it and reason about it. * Naming discussions tend to lead to endless bikeshed discussion. Naming stuff is easy so everybody has an opinion, including myself. It's not very productive. We don't have clear community mechanisms to make decisions either (the Zope Framework Steering Group isn't it; it only cares about the Zope Framework. Perhaps the Foundation can be it, but it can only approve initiatives from the community in this area, I think. In this context I'll mention the new name "Zope Framework" that was recently introduced and is probably not yet fully understood by everybody. The Zope Framework is a collection of libraries. It's shared by at least the following web frameworks/app servers: Zope 2 app server, Zope 3 app server, Grok. Other systems such as bfg use a much smaller subset of these libraries. I see this as following the principles above: * it's only introducing a single new name. That's why it at least gets some acceptance now. * it's naming something that we were really already talking about. Unfortunately we conflated it with "Zope 3", the thing you start that has a UI and so on, which retarded the development of both Zope 3 and the Zope Framework itself. It's good we have a handle on it now as a separate entity. This "Zope Framework" name and concept is just now percolating through the community. Zope Framework is *not* the renamed Zope 3, even though it's entirely based on what we used to call Zope 3. Zope 3 continues to exist, as long as there are people who are interested in creating an installation tool for it and care about its UI. Zope Framework is a *separate* entity. Zope 2 and Zope 3 do have confusing names. I prefer to tweak the meaning of "Zope" to be a project identifier instead of identifying software directly: Zope is all of the stuff developed by the Zope project. We therefore have the Zope Object Database, we have the zope component architecture, the zope interface package. This doesn't work for Zope 2 and Zope 3. It works for Grok by the way: I've been saying "Zope Grok" sometimes. With Zope 2 and Zope 3, we have version numbers that are at the same time identifiers of a piece of software itself; they're not really version numbers at all. That's why I have been using terms like Zope 2 App Server and Zope 3 App Server, but that isn't very satisfactory either. The 2 and the 3 still imply some kind of evolutionary progression that isn't quite what we are doing. In order to make Zope 2 and Zope 3 fit the pattern, it'd be nice if they had names that fit the "Zope is a project, not software" pattern. We could rename Zope 2 to Zope Classic, as was suggested. I think we should also rename Zope 3 to something else (that doesn't imply it's the modern future, as there are other alternatives at least as modern around that are more recently developed - we want to get out of that bind). I think renaming Zope 2 to Zope Classic will be easy. If the Zope 2 developers are okay with this, let's go right ahead. Not much discussion needed. Zope 2.11 becomes Zope Classic 11. It's a huge version number, but Zope Classic is over a decade old anyway. Nobody's going to mind. It looks impressive and it should be impressive; Zope Classic has been maintained for a long time by the community. I think it's going to be harder for Zope 3, as the "Zope 3" community: those people who care about Zope 3 as a piece of software that can be installed, hasn't fully formed yet. There's a tool called "zopeproject" which is quite misnamed in the light of the above discussion. While I sometimes do use that piece of software, I'm far more interested in the Zope Framework, myself. Anyway, I'm rather reluctant to post this as I fear this will be a pile-on bikeshed discussion. I'd suggest that anyone interested in naming Zope 3 something else should keep quiet for the time being. Go and form a Zope 3 interest group first, don't talk about naming too much yet in that either, and come back to this topic later. Let's talk about Zope Classic and see whether renaming Zope 2 to that is a step we can realistically take in the near future. Who is in favor of that? Regards, Martijn

21 71

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

12 Apr '09

Summary of messages to the zope-tests list. Period Sat Apr 11 12:00:00 2009 UTC to Sun Apr 12 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: Sat Apr 11 20:46:12 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011443.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Sat Apr 11 20:48:14 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011444.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Sat Apr 11 20:50:16 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011445.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Sat Apr 11 20:52:16 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011446.html Subject: OK : Zope-trunk Python-2.6.1 : Linux From: Zope Tests Date: Sat Apr 11 20:54:19 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011447.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Sat Apr 11 20:56:20 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011448.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Sat Apr 11 20:58:20 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011449.html Subject: OK : Zope-trunk-alltests Python-2.6.1 : Linux From: Zope Tests Date: Sat Apr 11 21:00:22 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011450.html

1 0

view lookup based on location
by Chris Withers 11 Apr '09

11 Apr '09

Hi All, Suppose I have the following: a = Folder() b = Folder() c = Folder() a.b = b a.c = c What's the canonical way of registering a view on b that is different to a view of the same name on a, and ditto with c? cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

2 1

zdaemon 2.0.3 released.
by Chris Withers 11 Apr '09

11 Apr '09

Hi All, I've just released zdaemon 2.0.3, from the changelog: - Added support to bootstrap on Jython. - If the run directory does not exist it will be created. This allow to use `/var/run/mydaemon` as run directory when /var/run is a tmpfs (LP #318118). Bugs Fixed ---------- - No longer uses a hardcoded filename (/tmp/demo.zdsock) in unit tests. This lets you run the tests on Python 2.4 and 2.5 simultaneously without spurious errors. - make -h work again for both runner and control scripts. Help is now taken from the __doc__ of the options class users by the zdaemon script being run. Once new Zope 2.12 and ZODB eggs are released, this will mean zeoctl -h, runzeo -h, zopectl -h and runzope -h will all work again :-) cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

1 0

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