April 2009 - Zope-Dev

conclusions from the "Who wants to maintain Zope 3" thread
by Martijn Faassen 14 Apr '09

14 Apr '09

Hi there, Closing that mega thread, here are some conclusions from it: * many people are quite willing to make sure their existing applications will still work. * people are quite willing to maintain the KGS for Zope 3 and release newer versions. In both cases, the scope of Zope 3 has decreased a lot, as most of the Zope 3 codebase will be shared with the Zope Toolkit, and the Zope 3 KGS will be based on the Zope Toolkit KGS. Concerning installation tools for Zope 3, it looks like some people are interested in this topic. We also discussed possible cooperation between the installation stories within a Zope Toolkit context. People have explicitly said they aren't interested in building-a-community related aspects of maintenance, such as writing documentation about how to install and use Zope 3, websites, etc. Concerning the ZMI, I haven't seen a lot of interest. People do use it in a minimal way to install apps, but the ZMI is rather more involved than that. I've started a new thread to explore that issue. Conclusions: It looks to me like we have support for a limited-scope Zope 3, possibly with a massively cut down ZMI that might be restricted to application installation (and documentation tools). The primary focus is to maintain existing applications, making sure they continue to work (much of that will be making sure the Zope Toolkit still works). So, it looks like Zope 3 will become a very thin layer on top of the Zope Toolkit. Technically this isn't that dissimilar from the way Grok uses the Zope Toolkit, though there's a vast difference in the community approach. Many people will just roll their own applications on top of the Zope Toolkit and may stop caring about Zope 3 altogether. Regards, Martijn

1 0

Zope Tests: 6 OK, 2 Failed
by Zope Tests Summarizer 14 Apr '09

14 Apr '09

Summary of messages to the zope-tests list. Period Mon Apr 13 12:00:00 2009 UTC to Tue Apr 14 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Test failures ------------- Subject: FAILED (failures=1) : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Mon Apr 13 21:00:09 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011461.html Subject: FAILED (failures=1) : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Mon Apr 13 21:06:11 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011464.html Tests passed OK --------------- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Mon Apr 13 20:56:05 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011459.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Mon Apr 13 20:58:06 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011460.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Mon Apr 13 21:02:10 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011462.html Subject: OK : Zope-trunk Python-2.6.1 : Linux From: Zope Tests Date: Mon Apr 13 21:04:10 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011463.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Mon Apr 13 21:08:11 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011465.html Subject: OK : Zope-trunk-alltests Python-2.6.1 : Linux From: Zope Tests Date: Mon Apr 13 21:10:11 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011466.html

1 0

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

13 Apr '09

Summary of messages to the zope-tests list. Period Sun Apr 12 12:00:00 2009 UTC to Mon Apr 13 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: Sun Apr 12 20:40:43 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011451.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Sun Apr 12 20:42:48 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011452.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Sun Apr 12 20:44:49 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011453.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Sun Apr 12 20:46:49 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011454.html Subject: OK : Zope-trunk Python-2.6.1 : Linux From: Zope Tests Date: Sun Apr 12 20:48:49 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011455.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Sun Apr 12 20:50:51 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011456.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Sun Apr 12 20:52:56 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011457.html Subject: OK : Zope-trunk-alltests Python-2.6.1 : Linux From: Zope Tests Date: Sun Apr 12 20:54:57 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011458.html

1 0

Zope 2.12 zpt "test" tab error: can other people reproduce this?
by Chris Withers 13 Apr '09

13 Apr '09

Hi All, In Zope 2.12, clicking the "Test" tab on a zpt in the zmi gives: Traceback (innermost last): Module ZPublisher.Publish, line 119, in publish Module ZPublisher.mapply, line 77, in mapply Module ZPublisher.Publish, line 42, in call_object Module Shared.DC.Scripts.Bindings, line 324, in __call__ Module Shared.DC.Scripts.Bindings, line 361, in _bindAndExec Module App.special_dtml, line 185, in _exec Module DocumentTemplate.DT_In, line 634, in renderwob Module DocumentTemplate.DT_Raise, line 68, in render Any ideas? Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

1 0

Five browser views and zpt macros?
by Chris Withers 13 Apr '09

13 Apr '09

Hi All, Am I right in thinking that in days gone by you could do: <browser:page for="*" name="standard_template.pt" template="standard_template.pt" permission="zope2.View" /> ...which would then allow you to use the macros from that zpt as follows: <html metal:use-macro="context/@@standard_template.pt/macros/main"> If so, how come this doesn't work in Zope 2.12 and what should I use instead? Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

1 0

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