May 2009 - Zope-Dev - Zope lists

zope 2.12.0a4 and CMFCore
by Jürgen Herrmann 04 May '09

04 May '09

i followed the directions in this thread: http://www.nabble.com/Zope-2.12.0a4-easy_installable---please-test-td232127… installation was fine with stock python2.4 on mandriva 2008.1 easy_install Products.CMFCore: installed without errors. on startup i get the following traceback: ... File "/home/xlhost/zope/GeneralProducts/utils/__init__.py", line 12, in ? from Products.TrustedExecutables.TrustedFSPageTemplate import TrustedFSPageTemplate File "/home/xlhost/zope/Products/TrustedExecutables/TrustedFSPageTemplate.py", line 3, in ? from Products.CMFCore.FSPageTemplate import FSPageTemplate, registerFileExtension File "/home/xlhost/zope/lib/python2.4/site-packages/Products.CMFCore-2.1.2-py2.4.egg/Products/CMFCore/__init__.py", line 26, in ? import PortalFolder File "/home/xlhost/zope/lib/python2.4/site-packages/Products.CMFCore-2.1.2-py2.4.egg/Products/CMFCore/PortalFolder.py", line 32, in ? from CMFCatalogAware import CMFCatalogAware File "/home/xlhost/zope/lib/python2.4/site-packages/Products.CMFCore-2.1.2-py2.4.egg/Products/CMFCore/CMFCatalogAware.py", line 31, in ? from interfaces import ICallableOpaqueItem File "/home/xlhost/zope/lib/python2.4/site-packages/Products.CMFCore-2.1.2-py2.4.egg/Products/CMFCore/interfaces/__init__.py", line 47, in ? from Interface.bridge import createZope3Bridge ImportError: No module named Interface.bridge any hints where to start hunting that bug? is it actually a bug? thanks in advance and best regards! jürgen herrmann -- >> XLhost.de - eXperts in Linux hosting ® << XLhost.de GmbH Jürgen Herrmann, Geschäftsführer Boelckestrasse 21, 93051 Regensburg, Germany Geschäftsführer: Volker Geith, Jürgen Herrmann Registriert unter: HRB9918 Umsatzsteuer-Identifikationsnummer: DE245931218 Fon: +49 (0)700 XLHOSTDE [0700 95467833] Fax: +49 (0)700 XLHOSTDE [0700 95467833] WEB: http://www.XLhost.de IRC: #XLhost(a)irc.quakenet.org

2 1

Zope Tests: 8 OK
by Zope Tests Summarizer 03 May '09

03 May '09

Summary of messages to the zope-tests list. Period Sat May 2 12:00:00 2009 UTC to Sun May 3 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 May 2 20:43:05 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011611.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Sat May 2 20:45:10 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011612.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Sat May 2 20:47:12 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011613.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Sat May 2 20:49:12 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011614.html Subject: OK : Zope-trunk Python-2.6.1 : Linux From: Zope Tests Date: Sat May 2 20:51:13 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011615.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Sat May 2 20:53:13 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011616.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Sat May 2 20:55:14 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011617.html Subject: OK : Zope-trunk-alltests Python-2.6.1 : Linux From: Zope Tests Date: Sat May 2 20:57:14 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011618.html

1 0

zope.testing broken!
by Roger Ineichen 02 May '09

02 May '09

Hi all The latest zope.testing is broken on windows. It uses subprocess with a not supported argument on windows (close_fds). Traceback (most recent call last): File "C:\Python25\lib\threading.py", line 486, in __bootstrap_inner self.run() File "C:\Python25\lib\threading.py", line 446, in run self.__target(*self.__args, **self.__kwargs) File "d:\home\.buildout\eggs\zope.testing-3.7.4-py2.5.egg\zope\testing\testrunner \runner.py", line 406, in spawn_layer_in_subprocess stdout=subprocess.PIPE, stderr=subprocess.PIPE, close_fds=True) File "C:\Python25\lib\subprocess.py", line 552, in __init__ raise ValueError("close_fds is not supported on Windows " ValueError: close_fds is not supported on Windows platforms Regards Roger Ineichen _____________________________ END OF MESSAGE

3 3

svn.zope.org b0rked?
by Andreas Jung 02 May '09

02 May '09

Hi, I tried several times to update my SVN checkouts (on different machines). After updating some svn:exernals, svn fails with something like svn: warning: Error handling externals definition for 'utilities/ZODBTools': svn: warning: Network connection closed unexpectedly Andreas

4 3

Zope Tests: 8 OK
by Zope Tests Summarizer 02 May '09

02 May '09

Summary of messages to the zope-tests list. Period Fri May 1 12:00:00 2009 UTC to Sat May 2 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 May 1 20:45:36 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011603.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Fri May 1 20:47:38 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011604.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Fri May 1 20:49:38 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011605.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Fri May 1 20:51:38 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011606.html Subject: OK : Zope-trunk Python-2.6.1 : Linux From: Zope Tests Date: Fri May 1 20:53:39 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011607.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Fri May 1 20:55:39 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011608.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Fri May 1 20:57:39 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011609.html Subject: OK : Zope-trunk-alltests Python-2.6.1 : Linux From: Zope Tests Date: Fri May 1 20:59:40 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011610.html

1 0

Re: [Zope-dev] Proposal: set __parent__ and __name__ in Zope 2.12 OFS
by Andreas Jung 01 May '09

01 May '09

On Sun, Apr 26, 2009 at 18:46, Martin Aspeli <optilude(a)gmail.com> wrote: > 2009/4/27 Andreas Jung <lists(a)zopyx.com>: > > > You might approach Hanno since he has committer rights. > > I do too... Does that mean you're +1 ? I have no problem with the changes. You have my blessing if Hanno is ok with the changes from the Plone prospective. Andreas

7 13

Proposal: set __parent__ and __name__ in Zope 2.12 OFS
by Martin Aspeli 01 May '09

01 May '09

Hi, First - a quick question: can we treat __name__ and id/getId()/_setId() as the same, always? OFS.SimpleItem has some support for letting id and name be the same, but the link is lost once both __name__ and id are set. Why isn't __name__ just a property that reflects self.id ? Then, the proposal: In Zope 2.12, acquisition wrappers are optional. Instead of using a wrapper, acquisition can work by following __parent__ pointers. That work well for views, where these are now set properly, but no content currently maintains __parent__ pointers. We can fix this by introducing some code in OFS (and BTreeFolder2) that mimics what zope.container does. We can't use the setitem() and uncontained() helpers directly, since these deal with containment proxies and have slightly different semantics, but I think we can do this: 1) Add the following to _setOb: def _setOb(self, id, object): if ILocation.providedBy(object): if not IContained.providedBy(object): alsoProvides(object, IContained) oldname = getattr(object, '__name__', None) oldparent = getattr(object, '__parent__', None) if id is not oldname: object.__name__ = id if self is not oldparent: object.__parent__ = self setattr(self, id, object) 2) Add the following to _delOb: def _delOb(self, id): """ Remove the named object from the folder. """ try: obj = self._getOb(id, _marker) if obj is not _marker: if IContained.providedBy(obj): obj.__parent__ = None obj.__name__ = None except AttributeError: # No need to fail if we can't set these pass delattr(self, id) Note that there's a slight discrepancy here with the way zope.container works. In Zope 3, the __parent__ pointer is not unset until after the ObjectRemovedEvent is fired. In Zope 2, we only fire that event after the object has been fully removed (in _delObject()), but we have the ObjectWillBeRemovedEvent that is fired before. I don't think this really matters, though. 3) It'd be nice to also make ObjectManager and BTreeFolder2Base support the IContainer interface, so that OFS containers can be used with the more natural dict-like API of Zope 3 rather than the somewhat obscure getattr()/_getOb()/_setObject()-vs-_setOb() and so on API we have now. To add this, we'd just need to add a few methods to ObjectManager that calls the existing APIs, e.g. __getitem__, __delitem__, __setitem__ and so on. We have code for all three of these in plone.folder which could be pushed down to OFS an BTreeFolder2 quite easily. Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book

10 17

Zope 2.12 from buildout with no funky recipes: success!
by Chris Withers 01 May '09

01 May '09

Hi All, I've committed the tiny change necessary to be able to run Zope 2.12 from a (relatively) simple buildout. I've attached the buildout.cfg, zope.conf.in and zeo.conf.in I've been using to this message. It would be nicer if the initialization bits could go away and the Zope2 egg could declare the runzope and zopectl scripts. Where do the runzeo and zeoctl entry points belong? I'd guess in the ZODB egg, but would they get built when specifying just the zope2 egg? The above may be problematic: how would we pass the location of zeo.conf and zope.conf to the start scripts? cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

2 3

Zope Tests: 8 OK
by Zope Tests Summarizer 01 May '09

01 May '09

Summary of messages to the zope-tests list. Period Thu Apr 30 12:00:00 2009 UTC to Fri May 1 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 30 20:45:18 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011595.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Thu Apr 30 20:47:21 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011596.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Thu Apr 30 20:49:27 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011597.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Thu Apr 30 20:51:27 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011598.html Subject: OK : Zope-trunk Python-2.6.1 : Linux From: Zope Tests Date: Thu Apr 30 20:53:27 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011599.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Thu Apr 30 20:55:27 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011600.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Thu Apr 30 20:57:27 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011601.html Subject: OK : Zope-trunk-alltests Python-2.6.1 : Linux From: Zope Tests Date: Thu Apr 30 20:59:28 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011602.html

1 0