December 2007 - Zope-Dev

unregistering components?
by Chris Withers 08 Feb '08

08 Feb '08

Hi All, Does the component architecture support un-registering adapters and the like? If not, what would it take to make it do so? cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

7 21

Request typing (to get the xmlrpc layer discussion finished)
by Christian Zagrodnick 17 Jan '08

17 Jan '08

Hi, a couple of weeks ago there was some discussion about the skin/layer support for XML-RPC which I implemented without asking (shame on me). As some time has passed now everybody could have some fresh thoughts about it. Let me first summarise: * Skin and layers should be seen as typing the request. * There are no general objections against having layers for XML-RPC. * There are objections against using ++skin++ for XML-RPC, ++api++ would be fine. Discussing the issue here at gocept again we've come to the following: There are different kinds of request (BrowserRequest, XMLRPCRequest, FTPRequest, …) which depend on the “channel” or server zope is accessed through. Then, depending on the kind of request, it often is desirable to further type the request: * a skin for browser requests * an API for xmlrpc requests * maybe different listings or content views for webdav We’d like to codify this understanding (the general concept of marking a request with a type) using a general IRequestType which all specific type implementations (skins, APIs, ...) are derived from. In our view this allows for understandably named implementations for each channel but still provide a common base. Therefore we propose to: * Create in zope.publisher.interfaces: class IRequestType(zope.interface.interfaces.IInterface): pass * Rename IXMLRPCSkinType to IXMLRPCAPIType(IRequestType) and create a traverser ++api++ for IXMLRPCApiType. * Use IRequestType as new base of IBrowserSkinType (instead of IInterface). * Do *not* provide any traverser for IRequestType since the traversers should be close to the “channel” so it is easy to understand what is happening. If the traverser name is too far fetched we end in confusion like with skin for xmlrpc. Regards, -- Christian Zagrodnick gocept gmbh & co. kg · forsterstrasse 29 · 06112 halle/saale www.gocept.com · fon. +49 345 12298894 · fax. +49 345 12298891

11 32

z3c.rml test failures
by Baiju M 16 Jan '08

16 Jan '08

Hi Stephan, I am getting some test failure in z3c.rml trunk. One issue is due to the use of non-existing 'font' tag. I can't find this tag in 'rml.dtd' and reference. (But I can see a single use of 'font' tag in reference, but it is in a different context, I think should should be replaced as described below) All the places where 'font' tag used is as a child of 'title' tag. And 'face' is the only attribute used for the font tag in tests. Now 'title' has a 'fontName' attribute, from the DTD and reference I deduced that tests should use this instead of 'font' tag, is it correct ? There is another issue when I run tests in level 2, this can be solved by using few more arguments to Popen . (see the patch attached) There is one more remaining issue while parsing 'tag-textField.xml' I have given the trace back below, but if I parse this file individually, there is no test failure ! May be this is due to tests are not cleaned up properly. Regards, Baiju M Error in test runTest (z3c.rml.tests.test_rml.tag-textField) Traceback (most recent call last): File "/baiju/usr//lib/python2.4/unittest.py", line 260, in run testMethod() File "/home/baiju/office/z298i/z3c.rml/src/z3c/rml/tests/test_rml.py", line 60, in runTest rml2pdf.go(self._inPath, self._outPath) File "/home/baiju/office/z298i/z3c.rml/src/z3c/rml/rml2pdf.py", line 64, in go doc.process(outputFile) File "/home/baiju/office/z298i/z3c.rml/src/z3c/rml/document.py", line 281, in process self.canvas.save() File "/home/baiju/office/z298i/z3c.rml/src/reportlab/pdfgen/canvas.py", line 877, in save self._doc.SaveToFile(self._filename, self) File "/home/baiju/office/z298i/z3c.rml/src/reportlab/pdfbase/pdfdoc.py", line 219, in SaveToFile f.write(self.GetPDFData(canvas)) File "/home/baiju/office/z298i/z3c.rml/src/reportlab/pdfbase/pdfdoc.py", line 241, in GetPDFData return self.format() File "/home/baiju/office/z298i/z3c.rml/src/reportlab/pdfbase/pdfdoc.py", line 384, in format IOf = IO.format(self) File "/home/baiju/office/z298i/z3c.rml/src/reportlab/pdfbase/pdfdoc.py", line 778, in format fcontent = format(content, document, toplevel=1) # yes this is at top level File "/home/baiju/office/z298i/z3c.rml/src/reportlab/pdfbase/pdfdoc.py", line 95, in format f = element.format(document) File "/home/baiju/office/z298i/z3c.rml/src/reportlab/pdfbase/pdfform.py", line 175, in format return proxy.format(document) File "/home/baiju/office/z298i/z3c.rml/src/reportlab/pdfbase/pdfpattern.py", line 54, in format L.append(format(value, document)) File "/home/baiju/office/z298i/z3c.rml/src/reportlab/pdfbase/pdfdoc.py", line 93, in format return document.Reference(element).format(document) File "/home/baiju/office/z298i/z3c.rml/src/reportlab/pdfbase/pdfdoc.py", line 475, in Reference raise ValueError, "object named but not registered" ValueError: object named but not registered

2 2

five.customerize
by Martijn Faassen 04 Jan '08

04 Jan '08

Hi there, So, I am trying to look at five.customerize in the context of Silva. I look at the SVN, and see the trunk is significantly older than various Plone-related branches. Hm, odd. I thought, let's download the 0.2 sources from the cheeseshop. I download them. Find out that they have dependencies on *Plone* in them. Having a hacked-up Plone branch is one thing, but having that released to the cheeseshop as *the* version isn't a very good idea. So, what's the plan to clean up this mess? Can the Plone specific stuff be cleared up from the branches into a Plone-specific package and a new release be made that works for both Plone and the rest of the Zope world? Regards, Martijn

3 7

Finding modification time for a specific file
by Saurabh Bagchi 02 Jan '08

02 Jan '08

I would like to do the following for a specific file, call it addMember.xls: 1) Print the name of the file. 2) By the side of the file, print its modification time. I can do this for all the files in the folder, but not for a specific file. I figure I need to pass some filter to objectValues to only select the specific file, but my attempts have been in vain so far. Thanks in advance for any help, Saurabh Help educate a child. http://www.purdue.edu/asha -- Saurabh Bagchi Dept. of Electrical & Computer Engineering, Purdue University. 465 Northwestern Avenue, West Lafayette, IN 47907. Phone: 765-494-3362(O); 765-497-1345(H); 765-427-5708(C) ____________________________________________________________________________________ Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping

2 1

Zope Tests: 4 OK, 1 Failed
by Zope Tests Summarizer 31 Dec '07

31 Dec '07

Summary of messages to the zope-tests list. Period Sun Dec 30 12:00:00 2007 UTC to Mon Dec 31 12:00:00 2007 UTC. There were 5 messages: 5 from Zope Unit Tests. Test failures ------------- Subject: FAILED (failures=1) : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Sun Dec 30 21:02:51 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-December/008880.html Tests passed OK --------------- Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Sun Dec 30 20:56:49 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-December/008876.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Sun Dec 30 20:58:20 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-December/008877.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Sun Dec 30 20:59:50 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-December/008878.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Sun Dec 30 21:01:20 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-December/008879.html

1 0

Zope Tests: 4 OK, 1 Failed
by Zope Tests Summarizer 30 Dec '07

30 Dec '07

Summary of messages to the zope-tests list. Period Sat Dec 29 12:00:00 2007 UTC to Sun Dec 30 12:00:00 2007 UTC. There were 5 messages: 5 from Zope Unit Tests. Test failures ------------- Subject: FAILED (failures=1) : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Sat Dec 29 20:58:29 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-December/008875.html Tests passed OK --------------- Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Sat Dec 29 20:52:28 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-December/008871.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Sat Dec 29 20:53:58 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-December/008872.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Sat Dec 29 20:55:29 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-December/008873.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Sat Dec 29 20:56:59 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-December/008874.html

1 0

Zope Tests: 4 OK, 1 Failed
by Zope Tests Summarizer 29 Dec '07

29 Dec '07

Summary of messages to the zope-tests list. Period Fri Dec 28 12:00:00 2007 UTC to Sat Dec 29 12:00:00 2007 UTC. There were 5 messages: 5 from Zope Unit Tests. Test failures ------------- Subject: FAILED (failures=1) : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Fri Dec 28 21:10:28 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-December/008870.html Tests passed OK --------------- Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Fri Dec 28 21:04:26 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-December/008866.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Fri Dec 28 21:05:57 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-December/008867.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Fri Dec 28 21:07:27 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-December/008868.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Fri Dec 28 21:08:58 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-December/008869.html

2 1

Re: [Zope 2.11] KGS incomplete (Was: Stepping forward and going beta)
by Andreas Jung 29 Dec '07

29 Dec '07

I wrote a small script to match the KGS against the current Zope/HEAD externals. The KGS is missing several zope.app modules that are used within Zope 2. What to do with them? WARN: KGS incomplete - BTrees not found WARN: KGS incomplete - ThreadedAsync not found WARN: KGS incomplete - ZEO not found WARN: KGS incomplete - ZODB not found WARN: KGS incomplete - ZopeUndo not found WARN: KGS incomplete - persistent not found WARN: KGS incomplete - transaction not found WARN: KGS incomplete - zope.app.content_types not found WARN: KGS incomplete - zope.app.event not found WARN: KGS incomplete - zope.app.filerepresentation not found WARN: KGS incomplete - zope.app.location not found WARN: KGS incomplete - zope.app.mail not found WARN: KGS incomplete - zope.app.rdb not found WARN: KGS incomplete - zope.app.servicenames not found WARN: KGS incomplete - zope.app.site not found WARN: KGS incomplete - zope.app.size not found WARN: KGS incomplete - zope.app.tests not found Andreas --On 24. Dezember 2007 04:54:50 +0100 Andreas Jung <lists(a)zopyx.com> wrote: > Thanks for pointing this out. I think I need to work on a script > to generate the textfiles for the externals in Zope 2 automatically > from the KGS :-> > > Happy x-mas, > Andreas > > --On 23. Dezember 2007 22:17:10 +0100 Philipp von Weitershausen > <philipp(a)weitershausen.de> wrote: > >> Andreas Jung wrote: >>> --On 18. Dezember 2007 21:53:55 +0100 Hanno Schlichting >>> <plone(a)hannosch.info> wrote: >>> >>>> Andreas Jung wrote: >>>>> the Zope 2.11 beta phase has been delayed for while. The reason for >>>>> holding but the release was Philipps and Hannos work on the >>>>> >>>>> <http://svn.zope.org/Zope/branches/philikon-aq/> >>>>> >>>>> branch. Unfortunately both can't work (lack of personal time) on the >>>>> branch and finish it in the feature. So I propose to release Zope 2.11 >>>>> beta 1 >>>>> by the end of the year w/o this branch. Zope 2.11 would contain the >>>>> Zope 3.4 and ZODB 3.8 with blob support as major new features. >>>>> >>>>> Objections? Thoughts? >>>> >>>> +1 btw. Is there an ETA for beta1? >>> >>> During x-mas and new year..likely around December 29th. If you need some >>> more days, let me know but I would like to push the beta 1 release asap. >> >> Note that doing a beta isn't just releasing the branch as it is. You >> should update all externals to the current 3.4.x releases of the >> individual eggs as well. The KGS [1] maintained by Stephan Richter >> provides you with a list of the most recent releases (except that the >> latest ZODB 3.8.0 candidate [2] isn't in it, apparently) >> >> Also please be careful not to add or remove packages arbitrarily from the >> externals. If I remember correctly, a while back somebody just copied the >> externals from the Zope 3 tree to Zope 2 and added a bunch of >> not-releasable software to Zope 2 and removed other stuff in the process. >> >> >> [1] http://download.zope.org/zope3.4/versions.cfg >> [2] http://cheeseshop.python.org/pypi/ZODB3/3.8.0c1 > > > > -- > ZOPYX Ltd. & Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany > Web: www.zopyx.com - Email: info(a)zopyx.com - Phone +49 - 7071 - 793376 > Registergericht: Amtsgericht Stuttgart, Handelsregister A 381535 > Geschäftsführer/Gesellschafter: ZOPYX Limited, Birmingham, UK > ------------------------------------------------------------------------ > E-Publishing, Python, Zope & Plone development, Consulting -- ZOPYX Ltd. & Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany Web: www.zopyx.com - Email: info(a)zopyx.com - Phone +49 - 7071 - 793376 Registergericht: Amtsgericht Stuttgart, Handelsregister A 381535 Geschäftsführer/Gesellschafter: ZOPYX Limited, Birmingham, UK ------------------------------------------------------------------------ E-Publishing, Python, Zope & Plone development, Consulting

4 14

buildbot for watching buildout projects on zope.org svn
by Christian Theune 28 Dec '07

28 Dec '07

Hi, I've moved the buildout configuration that I wrote a while ago to monitor buildout projects in the repository to its own (virtual) machine today. I'm still fiddling with the setup to make everything work with buildbot 0.7.6 which has some updates regarding in-flight reconfiguration and stability as well as an updated default Web UI in addition to the waterfall. I haven't re-enabled my layout yet, but the current one doesn't look too bad, maybe I'll integrate both together. The configuration is currently being re-read, so it might take a while until all buildout projects in svn.zope.org will show up again. Builds will be run after checkins to the monitored projects as well as at 3am UTC. I currently only monitor the trunk and anybody can press the build button. The slave will queue up requests if more than 10 builds are running at once. I'll probably have to reduce this number. I'll keep you updated. Christian -- gocept gmbh & co. kg - forsterstrasse 29 - 06112 halle (saale) - germany www.gocept.com - ct(a)gocept.com - phone +49 345 122 9889 7 - fax +49 345 122 9889 1 - zope and plone consulting and development

1 1