- Zope-Dev - Zope lists

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

11 Oct '09

Summary of messages to the zope-tests list. Period Sat Oct 10 12:00:00 2009 UTC to Sun Oct 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: Sat Oct 10 20:47:50 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-October/012752.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Sat Oct 10 20:49:50 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-October/012753.html Subject: OK : Zope-2.12 Python-2.4.6 : Linux From: Zope Tests Date: Sat Oct 10 20:51:50 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-October/012754.html Subject: OK : Zope-2.12-alltests Python-2.4.6 : Linux From: Zope Tests Date: Sat Oct 10 20:53:50 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-October/012755.html Subject: OK : Zope-2.12 Python-2.6.2 : Linux From: Zope Tests Date: Sat Oct 10 20:55:50 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-October/012756.html Subject: OK : Zope-2.12-alltests Python-2.6.2 : Linux From: Zope Tests Date: Sat Oct 10 20:57:50 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-October/012757.html Subject: OK : Zope-trunk Python-2.6.2 : Linux From: Zope Tests Date: Sat Oct 10 20:59:50 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-October/012758.html Subject: OK : Zope-trunk-alltests Python-2.6.2 : Linux From: Zope Tests Date: Sat Oct 10 21:01:50 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-October/012759.html

1 0

zope.security in the KGS
by John Murphy 11 Oct '09

11 Oct '09

We recently were bit by a segfault bug in zope.security (https://bugs.launchpad.net/zope3/+bug/181833) when migrating an application from Python 2.4 to 2.6. The newest zope.security (3.7.1, http://pypi.python.org/pypi/zope.security/3.7.1#id1) has a fix for the bug. We noticed that the KGS 3.4.0b2 uses zope.security 3.4.0 and KGS 3.5dev uses zope.security 3.6.0, both of which are vulnerable to this bug. It would be great if the fixed version was incorporated into the KGS soon, as segfaults during garbage collection are pretty serious -- not to mention tough to track down :) --Jackie Murphy

3 3

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

10 Oct '09

Summary of messages to the zope-tests list. Period Fri Oct 9 12:00:00 2009 UTC to Sat Oct 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: Fri Oct 9 20:45:09 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-October/012744.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Fri Oct 9 20:47:10 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-October/012745.html Subject: OK : Zope-2.12 Python-2.4.6 : Linux From: Zope Tests Date: Fri Oct 9 20:49:10 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-October/012746.html Subject: OK : Zope-2.12-alltests Python-2.4.6 : Linux From: Zope Tests Date: Fri Oct 9 20:51:10 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-October/012747.html Subject: OK : Zope-2.12 Python-2.6.2 : Linux From: Zope Tests Date: Fri Oct 9 20:53:10 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-October/012748.html Subject: OK : Zope-2.12-alltests Python-2.6.2 : Linux From: Zope Tests Date: Fri Oct 9 20:55:10 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-October/012749.html Subject: OK : Zope-trunk Python-2.6.2 : Linux From: Zope Tests Date: Fri Oct 9 20:57:10 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-October/012750.html Subject: OK : Zope-trunk-alltests Python-2.6.2 : Linux From: Zope Tests Date: Fri Oct 9 20:59:10 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-October/012751.html

1 0

Zope 2 documentation
by Baiju M 10 Oct '09

10 Oct '09

Hi Jens, I was looking at Zope 2 documentation. To generate this site : http://docs.zope.org/zope2/ we use the buildout available here, is it ? svn://svn.zope.org/repos/main/zope2docs/trunk So, can I remove the buildout available inside zdgbook and zope2book ? Also it looks like this patch is required to generate it locally: -----------------x<--------------x<-------------x<------------- Index: buildout.cfg =================================================================== --- buildout.cfg (revision 104937) +++ buildout.cfg (working copy) @@ -16,6 +16,7 @@ recipe = zc.recipe.egg eggs = Sphinx + docutils interpreter = stxpy scripts = sphinx-build Index: Makefile =================================================================== --- Makefile (revision 104937) +++ Makefile (working copy) @@ -3,7 +3,7 @@ # You can set these variables from the command line. SPHINXOPTS = -SPHINXBUILD = sphinx-build +SPHINXBUILD = ./bin/sphinx-build PAPER = # Internal variables. -----------------x<--------------x<-------------x<------------- May be we can pin the versions of Sphinx & docutils. Regards, Baiju M

3 7

ZTK sprint at ploneconf2009 Budapest
by Adam GROSZER 09 Oct '09

09 Oct '09

Hello, Feel free to join at http://www.coactivate.org/projects/ploneconf2009-ztk-sprint/project-home -- Best regards, Adam GROSZER mailto:agroszer@gmail.com -- Quote of the day: Democracy is a form of government in which it is permitted to wonder aloud what the country could do under first-class management. - Senator Soaper

1 0

Zope Tests: 8 OK
by Zope Tests Summarizer 09 Oct '09

09 Oct '09

Summary of messages to the zope-tests list. Period Thu Oct 8 12:00:00 2009 UTC to Fri Oct 9 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 Oct 8 20:45:54 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-October/012736.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Thu Oct 8 20:47:54 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-October/012737.html Subject: OK : Zope-2.12 Python-2.4.6 : Linux From: Zope Tests Date: Thu Oct 8 20:49:54 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-October/012738.html Subject: OK : Zope-2.12-alltests Python-2.4.6 : Linux From: Zope Tests Date: Thu Oct 8 20:51:54 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-October/012739.html Subject: OK : Zope-2.12 Python-2.6.2 : Linux From: Zope Tests Date: Thu Oct 8 20:53:54 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-October/012740.html Subject: OK : Zope-2.12-alltests Python-2.6.2 : Linux From: Zope Tests Date: Thu Oct 8 20:55:54 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-October/012741.html Subject: OK : Zope-trunk Python-2.6.2 : Linux From: Zope Tests Date: Thu Oct 8 20:57:54 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-October/012742.html Subject: OK : Zope-trunk-alltests Python-2.6.2 : Linux From: Zope Tests Date: Thu Oct 8 20:59:54 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-October/012743.html

1 0

Zope 2 WebDAV and acquisition
by Martin Aspeli 09 Oct '09

09 Oct '09

Hi, In my travails through the ZPublisher and WebDAV, I've come up with another fun thing. As far as I can tell, traversal via acquisition doesn't make any sense for a WebDAV request. If I have /foo and /bar, but not /bar/foo, then traversal to /bar/foo over WebDAV should not acquire /foo and wrap it in /bar. One reason for this (apart from being utterly confusing) is that it breaks PUT requests to a NullResource: If I try to PUT to /bar/foo it should create a new object there, not overwrite /foo. There is actually some convoluted support for detecting this in ZPublisher.BaseRequest: # Note - no_acquire_flag is necessary to support # things like DAV. We have to make sure # that the target object is not acquired # if the request_method is other than GET # or POST. Otherwise, you could never use # PUT to add a new object named 'test' if # an object 'test' existed above it in the # heirarchy -- you'd always get the # existing object :( if (no_acquire_flag and hasattr(parents[1], 'aq_base') and not hasattr(parents[1],'__bobo_traverse__')): if not (hasattr(parents[1].aq_base, entry_name) or parents[1].aq_base.has_key(entry_name)): raise AttributeError, entry_name This doesn't really work, though. The object is acquired, and then all it does is to check that the PUT() method object is a true attribute of the acquired object. But even then, raising AttributeError is wrong. What should happen, I think, is that in DefaultPublishTraverse.publishTraverse() we should *not* attempt to acquire for webdav requests. Instead, we should try direct attribute access and then __getitem__() access (which is the next thing it tries after getattr() acquisition). This would then allow the folder to return a NullResource (as OFS.ObjectManager does, for example). Any objections? It's a relatively simple condition in DfaultPublishTraverse.publishTraverse(). Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book

3 8

Re: [Zope-dev] SVN: zc.buildout/trunk/src/zc/buildout/buildout.py comparing requirement locations instead of requirement objects
by Martijn Faassen 08 Oct '09

08 Oct '09

Tarek Ziade wrote: > Log message for revision 104933: > comparing requirement locations instead of requirement objects Did I miss the CHANGES.txt update? Regards, Martijn

1 0

allow-picked-versions=false in ztk.cfg?
by Martijn Faassen 08 Oct '09

08 Oct '09

Hi there, To quote Thomas Lotze in another discussion: > [ztk.cfg] contains a line > allow-picked-versions = false > which makes buildout complain if it ends up using a package whose > version it had to pick from the index, so you're required to specify a > version for every package used by any part of the buildout. This line > is a piece of policy that I'd like to see gone from ztk.cfg as well; > if someone wants the behaviour, they can specify it in their > buildout.cfg. I agree with Thomas that we should remove this from ztk.cfg, as if we publish this for reuse we don't want to impose this policy on everybody who builds on it. The question though is why this is in there in the first place. Presumably it is to ensure that the *ZTK* locks down all versions. I think we can reasonably ensure this by moving the 'allow-picked-versions' to the ZTK's "buildout.cfg" instead, right? Regards, Martijn

6 12

Zope Tests: 8 OK
by Zope Tests Summarizer 08 Oct '09

08 Oct '09

Summary of messages to the zope-tests list. Period Wed Oct 7 12:00:00 2009 UTC to Thu Oct 8 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: Wed Oct 7 20:48:56 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-October/012728.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Wed Oct 7 20:50:56 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-October/012729.html Subject: OK : Zope-2.12 Python-2.4.6 : Linux From: Zope Tests Date: Wed Oct 7 20:52:56 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-October/012730.html Subject: OK : Zope-2.12-alltests Python-2.4.6 : Linux From: Zope Tests Date: Wed Oct 7 20:54:56 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-October/012731.html Subject: OK : Zope-2.12 Python-2.6.2 : Linux From: Zope Tests Date: Wed Oct 7 20:56:56 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-October/012732.html Subject: OK : Zope-2.12-alltests Python-2.6.2 : Linux From: Zope Tests Date: Wed Oct 7 20:58:56 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-October/012733.html Subject: OK : Zope-trunk Python-2.6.2 : Linux From: Zope Tests Date: Wed Oct 7 21:00:57 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-October/012734.html Subject: OK : Zope-trunk-alltests Python-2.6.2 : Linux From: Zope Tests Date: Wed Oct 7 21:02:57 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-October/012735.html

1 0