May 2009 - Zope-Dev - Zope lists

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

17 May '09

Summary of messages to the zope-tests list. Period Sat May 16 12:00:00 2009 UTC to Sun May 17 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 16 20:52:20 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011723.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Sat May 16 20:54:20 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011724.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Sat May 16 20:56:25 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011725.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Sat May 16 20:58:25 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011726.html Subject: OK : Zope-trunk Python-2.6.1 : Linux From: Zope Tests Date: Sat May 16 21:00:27 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011727.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Sat May 16 21:02:27 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011728.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Sat May 16 21:04:28 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011729.html Subject: OK : Zope-trunk-alltests Python-2.6.1 : Linux From: Zope Tests Date: Sat May 16 21:06:29 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011730.html

1 0

[Fwd: [Bug 376907] Re: AttributeError: 'str' object has no attribute 'registerSynch']
by Tim Cook 16 May '09

16 May '09

This is a bug I filed against ZODB3.9.0b1 As you can see Jim says it is a bug in zope.app.publication but there is no Launchpad project to forward the bug to for this module. The full text of the bug report is below the double lines. Thanks, Tim -------- Forwarded Message -------- From: Jim Fulton <jim(a)zope.com> Reply-to: Bug 376907 <376907(a)bugs.launchpad.net> To: timothywayne.cook(a)gmail.com Subject: [Bug 376907] Re: AttributeError: 'str' object has no attribute 'registerSynch' Date: Fri, 15 May 2009 12:53:47 -0000 This is a bug in zope.app.publication. It shouldn't pass a version to open. ** Changed in: zodb Status: New => Won't Fix ========================================================================================== ZODB3.9.0b1 - Linux x86_64 AMD - Grok 10a3. Server starts. Creates a new Data.fs, etc. When attempting to open http://localhost:8080/applications to add my Grok apps I get this error. Traceback here: ================================= 2009-05-15 08:30:05,890 ERROR [SiteError] http://localhost:8080 Traceback (most recent call last): File "/home/tim/.buildout/eggs/zope.publisher-3.4.6-py2.5.egg/zope/publisher/publish.py", line 129, in publish obj = publication.getApplication(request) File "/home/tim/.buildout/eggs/grok-1.0a3-py2.5.egg/grok/publication.py", line 70, in getApplication result = super(ZopePublicationSansProxy, self).getApplication(request) File "/home/tim/.buildout/eggs/zope.app.publication-3.4.3-py2.5.egg/zope/app/publication/zopepublication.py", line 150, in getApplication conn = self.db.open(version) File "/home/tim/.buildout/eggs/ZODB3-3.9.0b1-py2.5-linux-x86_64.egg/ZODB/DB.py", line 759, in open result.open(transaction_manager) File "/home/tim/.buildout/eggs/ZODB3-3.9.0b1-py2.5-linux-x86_64.egg/ZODB/Connection.py", line 1052, in open transaction_manager.registerSynch(self) AttributeError: 'str' object has no attribute 'registerSynch' =======================================================================================

2 3

Using views for exceptions in Zope 2.12?
by Chris Withers 16 May '09

16 May '09

Hi All, Given that the source of bug #372632 appears to be code related to allowing views on exceptions in Zope 2, I thought I'd try use this method. I tried this, without much joy: <browser:defaultView for="exceptions.Exception" name="error" /> <browser:page for="exceptions.Exception" template="html/error.html" name="error" permission="zope2.Public" /> So, how should I be wiring in views for exceptions? Also, is there a base view class for exceptions anywhere that provides the following or their equivalents? kwargs = {'error_type': error_name, 'error_value': error_value, 'error_tb': error_tb, 'error_traceback': error_tb, 'error_message': error_message, 'error_log_url': error_log_url} Finally, when a view is used to render and exception, is the userthe current logged in user (as is the case with standard_error_message) or Anonymous (as has annoyingly been the case with Unauthorized exceptions in the past) cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

5 6

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

16 May '09

Summary of messages to the zope-tests list. Period Fri May 15 12:00:00 2009 UTC to Sat May 16 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 15 20:51:55 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011715.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Fri May 15 20:54:00 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011716.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Fri May 15 20:56:00 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011717.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Fri May 15 20:58:04 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011718.html Subject: OK : Zope-trunk Python-2.6.1 : Linux From: Zope Tests Date: Fri May 15 21:00:05 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011719.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Fri May 15 21:02:06 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011720.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Fri May 15 21:04:06 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011721.html Subject: OK : Zope-trunk-alltests Python-2.6.1 : Linux From: Zope Tests Date: Fri May 15 21:06:07 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011722.html

1 0

zope.container analysis
by Chris McDonough 15 May '09

15 May '09

zope.container (32 transitive dependencies) has some possibly low-hanging dependency tease-apart fruit. Does anyone have any ideas about to sort out the below, particularly with externalizing the mentioned interface dependencies? - It depends on zope.filerepresentation but depends only on its interfaces IReadDirectory, IWriteDirectory, and IDirectoryFactory. (zope.filerepresentation has 32 transitive dependencies). - It depends on zope.app.dependable but depends only on its interfaces IDependable and DependencyError. (note: zope.app.dependable might be a candidate to be called zope.dependable as it depends on no other zope.app packages; it does depend on about 20 other zope.* packages transitively tho). - It depends on zope.publisher, but only its interfaces browser.IBrowserRequest, browser.IBrowserPublisher, NotFound, IDefaultViewName, xmlrpc.IXMLRPCPublisher, and IPublishTraverse. - I was able to break a runtime logic dependency on zope.traversing by disusing zope.traversing.api.getPath in favor of using ILocationInfo(object).getPath(). The rest of the runtime dependencies on zope.traversing are interface dependencies (ITraversable, IContainmentRoot).

5 7

Re: [Zope-dev] [Checkins] SVN: zope.intid/trunk/ - Remove a dependency on ``zope.container.contained.Contained``
by Michael Howitz 15 May '09

15 May '09

Am 15.05.2009 um 05:32 schrieb Chris McDonough: > Log message for revision 99961: > - Remove a dependency on ``zope.container.contained.Contained`` > (this is a dumb base class that defines __parent__ and __name__ > as None and declares that the class implements IContained). What's the reason behind this refactoring? Instead of zope.container.contained.Contained the IntIds class now depends on zope.container.interface.IContained plus it redefines the things which are already defined in zope.container.contained.Contained. I do not see why this is better than using the base class. > Changed: > U zope.intid/trunk/CHANGES.txt > U zope.intid/trunk/src/zope/intid/__init__.py [...] > Modified: zope.intid/trunk/src/zope/intid/__init__.py > ===================================================== > --- zope.intid/trunk/src/zope/intid/__init__.py 2009-05-15 02:41:49 > UTC (rev 99960) > +++ zope.intid/trunk/src/zope/intid/__init__.py 2009-05-15 03:31:59 > UTC (rev 99961) > @@ -24,10 +24,9 @@ > > import BTrees > from persistent import Persistent > -from ZODB.interfaces import IConnection > from zope.component import adapter, getAllUtilitiesRegisteredFor, > subscribers > from zope.container.interfaces import IObjectAddedEvent, > IObjectRemovedEvent > -from zope.container.contained import Contained > +from zope.container.interfaces import IContained > from zope.event import notify > from zope.interface import implements > from zope.keyreference.interfaces import IKeyReference, NotYet > @@ -37,14 +36,16 @@ > from zope.intid.interfaces import IIntIds, IIntIdEvent > from zope.intid.interfaces import IntIdAddedEvent, IntIdRemovedEvent > > -class IntIds(Persistent, Contained): > +class IntIds(Persistent): > """This utility provides a two way mapping between objects and > integer ids. > > IKeyReferences to objects are stored in the indexes. > """ > - implements(IIntIds) > + implements(IIntIds, IContained) > > + __parent__ = __name__ = None > + > _v_nextid = None Yours sincerely, -- Michael Howitz · mh(a)gocept.com · software developer gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 8 · fax +49 345 1229889 1 Zope and Plone consulting and development

6 8

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

15 May '09

Summary of messages to the zope-tests list. Period Thu May 14 12:00:00 2009 UTC to Fri May 15 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 May 14 20:54:45 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011707.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Thu May 14 20:57:05 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011708.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Thu May 14 20:59:06 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011709.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Thu May 14 21:01:06 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011710.html Subject: OK : Zope-trunk Python-2.6.1 : Linux From: Zope Tests Date: Thu May 14 21:03:06 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011711.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Thu May 14 21:05:06 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011712.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Thu May 14 21:07:07 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011713.html Subject: OK : Zope-trunk-alltests Python-2.6.1 : Linux From: Zope Tests Date: Thu May 14 21:09:07 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011714.html

1 0

z3c.recipe.i18n tests break on unix
by Christian Zagrodnick 15 May '09

15 May '09

Hi, the tests of z3c.reipce.i18n break on unix systems, for instance with: Failed example: ls('bin') Expected: - buildout-script.py - buildout.exe - i18ncompile-script.py - i18ncompile.exe - i18nextract-script.py - i18nextract.exe - i18nmergeall-script.py - i18nmergeall.exe - i18nstats-script.py - i18nstats.exe Got: - buildout - i18ncompile - i18nextract - i18nmergeall - i18nstats What's the general way of testing those things in both environments? I don't have a windows box to test this. I also see most recipes are tested only for unix (which would be fine for me). How should we proceed in this special case? Actually there is a bug which I'm going to fix w/o having passing tests now. Regards, -- Christian Zagrodnick · cz(a)gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 4 · fax +49 345 1229889 1 Zope and Plone consulting and development

3 4

"ZTK" futures: one big package?
by Chris McDonough 14 May '09

14 May '09

I was just thinking about the future of the "ZTK", and in the past I have argued for not attempting to version the entire set of packages that currently comprises Zope 3 over time as "ZTK releases". Instead, I have argued for promoting packages that have some life of their own (independent of the rest of the pile) into subprojects that have their own release cycles. Then outside projects such as Plone and Grok could depend on independent versions of such packages, giving them slightly more flexibility than requiring a "version of the ZTK". Given that this suggestion has been met with skepticism, let me try another tact. Instead of thinking about it this way, could we think about it as *deflating* the current set of zope.* packages that do not currently have a meaningful life of their own into a single setuptools distribution named "ZTK". This package would include most everything in zope.app*, plus things like zope.server, zope.publisher, and other things that just aren't useful outside of Zope-the-appserver, or which currently just depend on "too much". This "ZTK" distribution would *not* include packages that already have a life of their own outside Zope such as zope.interface, zope.component, zope.configuration, zope.proxy, ZODB, etc. These packages would continue to have their own release cycles. Over time, we'd tease out the dependencies of packages that live in the ZTK distribution, making them useful outside without any dependency on the ZTK. The names of these packages could be arbitrary (they wouldn't need to retain their old "zope.*" names). Some backwards dependency shims would be added to the ZTK to prevent old imports from breaking, and the ZTK distribution would then just have a dependency on the thing that got broken out. I'm thinking that this would simplify things greatly for people who want to be consumers of "truly independent" Zope packages. There'd be exactly N of them available for download (where N is much less than 100, more like 20), plus the ZTK, which would have the rest of the pile in it over time. If someone wanted to use a forked version of a package that lived in the ZTK distribution, they'd either do so by teasing out the dependencies and making it "truly independent" or they'd just reroll a custom version of the entire ZTK distribution. Does this make any sense? - C - C

11 40

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

14 May '09

Summary of messages to the zope-tests list. Period Wed May 13 12:00:00 2009 UTC to Thu May 14 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 May 13 20:51:45 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011699.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Wed May 13 20:53:46 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011700.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Wed May 13 20:55:47 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011701.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Wed May 13 20:57:47 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011702.html Subject: OK : Zope-trunk Python-2.6.1 : Linux From: Zope Tests Date: Wed May 13 20:59:47 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011703.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Wed May 13 21:01:47 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011704.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Wed May 13 21:03:47 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011705.html Subject: OK : Zope-trunk-alltests Python-2.6.1 : Linux From: Zope Tests Date: Wed May 13 21:05:48 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011706.html

1 0