July 2009 - Zope-Dev

Zope Tests: 3 OK, 5 Failed
by Zope Tests Summarizer 22 Jul '09

22 Jul '09

Summary of messages to the zope-tests list. Period Tue Jul 21 12:00:00 2009 UTC to Wed Jul 22 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Test failures ------------- Subject: FAILED (failures=1) : Zope-2.12 Python-2.6.2 : Linux From: Zope Tests Date: Tue Jul 21 20:49:49 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012114.html Subject: FAILED (failures=1) : Zope-2.12-alltests Python-2.4.6 : Linux From: Zope Tests Date: Tue Jul 21 20:51:49 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012115.html Subject: FAILED (failures=7) : Zope-2.12-alltests Python-2.6.2 : Linux From: Zope Tests Date: Tue Jul 21 20:53:50 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012116.html Subject: FAILED (failures=1) : Zope-trunk Python-2.6.2 : Linux From: Zope Tests Date: Tue Jul 21 20:55:50 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012117.html Subject: FAILED (failures=7) : Zope-trunk-alltests Python-2.6.2 : Linux From: Zope Tests Date: Tue Jul 21 20:57:50 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012118.html Tests passed OK --------------- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Tue Jul 21 20:43:49 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012111.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Tue Jul 21 20:45:49 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012112.html Subject: OK : Zope-2.12 Python-2.4.6 : Linux From: Zope Tests Date: Tue Jul 21 20:47:49 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012113.html

1 0

Zope Tests: 3 OK, 5 Failed
by Zope Tests Summarizer 21 Jul '09

21 Jul '09

Summary of messages to the zope-tests list. Period Mon Jul 20 12:00:00 2009 UTC to Tue Jul 21 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Test failures ------------- Subject: FAILED (failures=1) : Zope-2.12 Python-2.6.2 : Linux From: Zope Tests Date: Mon Jul 20 20:49:48 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012106.html Subject: FAILED (failures=1) : Zope-2.12-alltests Python-2.4.6 : Linux From: Zope Tests Date: Mon Jul 20 20:51:48 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012107.html Subject: FAILED (failures=7) : Zope-2.12-alltests Python-2.6.2 : Linux From: Zope Tests Date: Mon Jul 20 20:53:48 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012108.html Subject: FAILED (failures=1) : Zope-trunk Python-2.6.2 : Linux From: Zope Tests Date: Mon Jul 20 20:55:49 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012109.html Subject: FAILED (failures=7) : Zope-trunk-alltests Python-2.6.2 : Linux From: Zope Tests Date: Mon Jul 20 20:57:49 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012110.html Tests passed OK --------------- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Mon Jul 20 20:43:48 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012103.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Mon Jul 20 20:45:48 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012104.html Subject: OK : Zope-2.12 Python-2.4.6 : Linux From: Zope Tests Date: Mon Jul 20 20:47:48 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012105.html

1 0

how to prevent the pagetemplate reload?
by YoungKing 21 Jul '09

21 Jul '09

Hi all, I see the pagetemplate reload on each time modified,this may be bad for the production environment,how to prevent it ? devmode off in the zope.conf seems not to work. I notice that there's an option ``reload_templates`` in repoze.bfg,does zope3 has the same thing?

2 1

Broken authentication with zope.app.component 3.4.1 BBB code
by Marius Gedminas 20 Jul '09

20 Jul '09

I've a bit of fun debugging an authentication issue in an application that recently upgraded to Zope 3.4 (using the 3.4.0 KGS). The issue was that groups defined in ZCML (such as zope.Everybody) did not get applied to principals (if "applied" is the right word here). Debugging this led me to this quiet little marvel of code in zope.securitypolicy.zopepolicy: try: group = getPrincipal(group_id) except PrincipalLookupError: # It's bad if we have an undefined principal, # but we don't want to fail here. But we won't # honor any grants for the group. We'll just skip it. continue and from there to zope.app.authentication.authentication def getPrincipal(self, id): if not id.startswith(self.prefix): next = queryNextUtility(self, IAuthentication) if next is None: raise PrincipalLookupError(id) return next.getPrincipal(id) where queryNextUtility unexpectedly returned None instead of chaining to the global IAuthentication utility, which would know about groups such as 'zope.Everybody'. Comparing the database I have here (which has been in production for years) with a freshly-created new database I noticed a difference in LocalSiteManager's attributes: old db had __bases__ == (), new db had __bases__ = (<BaseGlobalComponents>, ). An hour of cursing and fighting buildout.cfg later, I had a branch of zope.app.component where I could run the test suite. I could reproduce the issue in the unit tests and released a fix as zope.app.component 3.4.2. This is a pretty serious issue, so I'd appreciate some review from people who know about local component registries. The fix is here: http://svn.zope.org/zope.app.component/?rev=101931&view=rev I'm also wondering whether we ought to release an updated versions.cfg (as Zope KGS 3.4.1 perhaps), since the BBB issue is insidious and difficult to notice. Marius Gedminas -- http://pov.lt/ -- Zope 3 consulting and development

3 7

Zope Tests: 3 OK, 5 Failed
by Zope Tests Summarizer 20 Jul '09

20 Jul '09

Summary of messages to the zope-tests list. Period Sun Jul 19 12:00:00 2009 UTC to Mon Jul 20 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Test failures ------------- Subject: FAILED (failures=1) : Zope-2.12 Python-2.6.2 : Linux From: Zope Tests Date: Sun Jul 19 20:49:49 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012098.html Subject: FAILED (failures=1) : Zope-2.12-alltests Python-2.4.6 : Linux From: Zope Tests Date: Sun Jul 19 20:51:49 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012099.html Subject: FAILED (failures=7) : Zope-2.12-alltests Python-2.6.2 : Linux From: Zope Tests Date: Sun Jul 19 20:53:49 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012100.html Subject: FAILED (failures=1) : Zope-trunk Python-2.6.2 : Linux From: Zope Tests Date: Sun Jul 19 20:55:49 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012101.html Subject: FAILED (failures=7) : Zope-trunk-alltests Python-2.6.2 : Linux From: Zope Tests Date: Sun Jul 19 20:57:49 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012102.html Tests passed OK --------------- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Sun Jul 19 20:43:48 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012095.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Sun Jul 19 20:45:48 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012096.html Subject: OK : Zope-2.12 Python-2.4.6 : Linux From: Zope Tests Date: Sun Jul 19 20:47:49 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012097.html

1 0

Zope Tests: 3 OK, 5 Failed
by Zope Tests Summarizer 19 Jul '09

19 Jul '09

Summary of messages to the zope-tests list. Period Sat Jul 18 12:00:00 2009 UTC to Sun Jul 19 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Test failures ------------- Subject: FAILED (failures=1) : Zope-2.12 Python-2.6.2 : Linux From: Zope Tests Date: Sat Jul 18 20:50:01 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012090.html Subject: FAILED (failures=1) : Zope-2.12-alltests Python-2.4.6 : Linux From: Zope Tests Date: Sat Jul 18 20:52:01 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012091.html Subject: FAILED (failures=7) : Zope-2.12-alltests Python-2.6.2 : Linux From: Zope Tests Date: Sat Jul 18 20:54:01 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012092.html Subject: FAILED (failures=1) : Zope-trunk Python-2.6.2 : Linux From: Zope Tests Date: Sat Jul 18 20:56:01 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012093.html Subject: FAILED (failures=7) : Zope-trunk-alltests Python-2.6.2 : Linux From: Zope Tests Date: Sat Jul 18 20:58:01 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012094.html Tests passed OK --------------- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Sat Jul 18 20:44:01 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012087.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Sat Jul 18 20:46:01 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012088.html Subject: OK : Zope-2.12 Python-2.4.6 : Linux From: Zope Tests Date: Sat Jul 18 20:48:01 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012089.html

1 0

Re: [Zope-dev] [Checkins] SVN: z3c.form/branches/icemac_compatibility/ - Made compatible with `zope.app.publisher` 3.8.2
by Michael Howitz 17 Jul '09

17 Jul '09

Am 17.07.2009 um 18:24 schrieb Michael Howitz: > Log message for revision 101967: > - Made compatible with `zope.app.publisher` 3.8.2 (and above) by > using > the new absolute url adapter for resources introduced in 3.8.2. The current trunk of z3c.form is not compatible with zope.app.publisher 3.8.2 and above, as this version introduced an absolute url adapter for resources. This adapter does not exist in versions before 3.8.2. It returns a str instead of a unicode as Resource.__call__ did before. (Relying on this feature seems to be bad anyway.) So my question is whether z3c.form 2.x still has to be compatible with KGS 3.4 of if we can break this compatibility to get compatible with more recent versions of other packages. Trying to stay compatible requires at least some conditional code to register the new absolute url adapter in the tests. Is there any buildbot which tests z3c.form against KGS 3.4 and above? > - Fixed tests to run with `z3c.pt` 1.0b17 (and above) by adding a > missing test dependency on `zope.app.component`. This is necessary because zope.app.component no longer gets pulled in indirectly. But z3c.pt expects zope.app.component to be installed when zope.app.security is installed. (zope.app.security is a test dependency needed by browser/README.txt) zope.app.component is even required for one test (browser/README.txt) of z3c.form. > Changed: > U z3c.form/branches/icemac_compatibility/CHANGES.txt > U z3c.form/branches/icemac_compatibility/buildout.cfg > U z3c.form/branches/icemac_compatibility/setup.py > U z3c.form/branches/icemac_compatibility/src/z3c/form/browser/ > README.txt > U z3c.form/branches/icemac_compatibility/src/z3c/form/browser/ > image.py > U z3c.form/branches/icemac_compatibility/src/z3c/form/button.py > U z3c.form/branches/icemac_compatibility/src/z3c/form/button.txt > > -=- > Modified: z3c.form/branches/icemac_compatibility/CHANGES.txt > =================================================================== > --- z3c.form/branches/icemac_compatibility/CHANGES.txt 2009-07-17 > 16:22:39 UTC (rev 101966) > +++ z3c.form/branches/icemac_compatibility/CHANGES.txt 2009-07-17 > 16:24:27 UTC (rev 101967) > @@ -12,6 +12,13 @@ > manager is only registered for dict, because it would otherwise get > picked up in undesired scenarios. > > +- Made compatible with `zope.app.publisher` 3.8.2 (and above) by > using > + the new absolute url adapter for resources introduced in 3.8.2. > + > +- Fixed tests to run with `z3c.pt` 1.0b17 (and above) by adding a > + missing test dependency on `zope.app.component`. > + > + > Version 2.0.0 (2009-06-14) > -------------------------- > > > Modified: z3c.form/branches/icemac_compatibility/buildout.cfg > =================================================================== > --- z3c.form/branches/icemac_compatibility/buildout.cfg 2009-07-17 > 16:22:39 UTC (rev 101966) > +++ z3c.form/branches/icemac_compatibility/buildout.cfg 2009-07-17 > 16:24:27 UTC (rev 101967) > @@ -2,7 +2,12 @@ > develop = . benchmark > parts = test test-no-z3cpt checker coverage-test coverage-report > docs i18n > benchmark python > +versions = versions > > +[versions] > +zope.app.publisher = 3.8.3 > +z3c.pt = 1.0.0 > + > [test-environment] > CHAMELEON_DEBUG = False > CHAMELEON_CACHE = False > > Modified: z3c.form/branches/icemac_compatibility/setup.py > =================================================================== > --- z3c.form/branches/icemac_compatibility/setup.py 2009-07-17 > 16:22:39 UTC (rev 101966) > +++ z3c.form/branches/icemac_compatibility/setup.py 2009-07-17 > 16:24:27 UTC (rev 101967) > @@ -91,6 +91,8 @@ > 'zope.app.testing', > 'zope.container', > 'zope.testing', > + 'zope.app.component', # required by z3c.pt from 1.0b17 on > + # also required by our browser/ > README.txt > ], > adding = ['zope.app.container'], > docs = ['z3c.recipe.sphinxdoc'], > > Modified: z3c.form/branches/icemac_compatibility/src/z3c/form/ > browser/README.txt > =================================================================== > --- z3c.form/branches/icemac_compatibility/src/z3c/form/browser/ > README.txt 2009-07-17 16:22:39 UTC (rev 101966) > +++ z3c.form/branches/icemac_compatibility/src/z3c/form/browser/ > README.txt 2009-07-17 16:24:27 UTC (rev 101967) > @@ -500,6 +500,14 @@ >>>> zope.component.provideAdapter( > ... resource, (None, None), ITraversable, name="resource") > > + # Register resource absolute url adapter > + >>> import zope.app.publisher.browser.resource > + >>> from zope.app.publisher.interfaces import IResource > + >>> import zope.traversing.browser.interfaces > + >>> zope.component.provideAdapter( > + ... zope.app.publisher.browser.resource.AbsoluteURL, > (IResource, None), > + ... zope.traversing.browser.interfaces.IAbsoluteURL) > + > # Register the "pressme.png" resource >>>> from zope.app.publisher.browser.resource import Resource >>>> testing.browserResource('pressme.png', Resource) > > Modified: z3c.form/branches/icemac_compatibility/src/z3c/form/ > browser/image.py > =================================================================== > --- z3c.form/branches/icemac_compatibility/src/z3c/form/browser/ > image.py 2009-07-17 16:22:39 UTC (rev 101966) > +++ z3c.form/branches/icemac_compatibility/src/z3c/form/browser/ > image.py 2009-07-17 16:24:27 UTC (rev 101967) > @@ -51,6 +51,6 @@ > image.value = field.title > # Get the full resource URL for the image: > site = hooks.getSite() > - image.src = zope.traversing.api.traverse( > - site, '++resource++' + field.image, request=request)() > + image.src = unicode(zope.traversing.api.traverse( > + site, '++resource++' + field.image, request=request)()) > return image > > Modified: z3c.form/branches/icemac_compatibility/src/z3c/form/ > button.py > =================================================================== > --- z3c.form/branches/icemac_compatibility/src/z3c/form/button.py > 2009-07-17 16:22:39 UTC (rev 101966) > +++ z3c.form/branches/icemac_compatibility/src/z3c/form/button.py > 2009-07-17 16:24:27 UTC (rev 101967) > @@ -234,8 +234,8 @@ > @property > def src(self): > site = hooks.getSite() > - src = zope.traversing.api.traverse( > - site, '++resource++' + self.field.image, > request=self.request)() > + src = unicode(zope.traversing.api.traverse( > + site, '++resource++' + self.field.image, > request=self.request)()) > return src > > def isExecuted(self): > > Modified: z3c.form/branches/icemac_compatibility/src/z3c/form/ > button.txt > =================================================================== > --- z3c.form/branches/icemac_compatibility/src/z3c/form/button.txt > 2009-07-17 16:22:39 UTC (rev 101966) > +++ z3c.form/branches/icemac_compatibility/src/z3c/form/button.txt > 2009-07-17 16:24:27 UTC (rev 101967) > @@ -644,6 +644,14 @@ >>>> zope.component.provideAdapter( > ... resource, (None, None), ITraversable, name="resource") > > + # Register resource absolute url adapter > + >>> import zope.app.publisher.browser.resource > + >>> from zope.app.publisher.interfaces import IResource > + >>> import zope.traversing.browser.interfaces > + >>> zope.component.provideAdapter( > + ... zope.app.publisher.browser.resource.AbsoluteURL, > (IResource, None), > + ... zope.traversing.browser.interfaces.IAbsoluteURL) > + > # Register the "submit.png" resource >>>> from zope.app.publisher.browser.resource import Resource >>>> testing.browserResource('submit.png', Resource) 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

2 1

z3c.recipe.i18n and zope.app.locales.extract
by yuppie 17 Jul '09

17 Jul '09

Hi! I plan to use z3c.recipe.i18n for some Zope 2 CMF products. But to get things working I did have to modify z3c.recipe.i18n a bit. It would be nice if I could get some feedback regarding the issues I found: 1.) running tests ----------------- test.py tries to install 'zodbcode' and 'zope.app.interface'. That doesn't work for me. AFAICS those two eggs are no longer indirect testing dependencies. After removing those two lines all tests pass. Proposal: Remove those two lines in test.py. 2.) looking up the product version ---------------------------------- POTMaker._getProductVersion() doesn't work for me. zope.app.applicationcontrol is not used by Zope 2 and is not part of the specified dependencies. This raises an error. Proposal: Catch the error. Return an empty string if version is not found. 3.) customizing the .pot header ------------------------------- POTMaker.write() uses a harcoded Zope 3 specific pot_header template. Proposal: The easiest and most flexible way to customize this seems to be an option that allows to specify a file that contains the pot_header template. 4.) looking up basePath ----------------------- i18nextract.main() contains these lines: # add maker for each given path for pkgName, path in eggPaths: srcIdx = path.rfind('src') if srcIdx == -1: # this is an egg package, strip down base path basePath = path moduleNames = pkgName.split('.') moduleNames.reverse() for mName in moduleNames: mIdx = path.rfind(mName) basePath = basePath[:mIdx] pkgPath = path[len(basePath):] else: # this is a package linked in as externals basePath = path[:srcIdx] pkgPath = path[len(basePath):] I don't understand why we need different code for "packages linked in as externals". The "egg package" code works actually better for linked in packages that don't follow the 'src' convention. Proposal: Use the 'if' code for all packages. 5. writing makers ----------------- I'd like to specify additional makers. This is a nice hook, but why are only these three arguments passed to custom poMakers? maker.add(poMaker(path, basePath, exclude_dirs), basePath) I miss 'domain' and 'include_default_domain'. Proposal: Pass in the additional arguments and fall back to the old signature for BBB. Does all that make sense? Any objections or better ideas? Should changes for POTMaker go into zope.app.locales.extract or should z3c.recipe.i18n use a customized version? Cheers, Yuppie

2 7

Zope Tests: 2 OK, 4 Failed
by Zope Tests Summarizer 17 Jul '09

17 Jul '09

Summary of messages to the zope-tests list. Period Thu Jul 16 12:00:00 2009 UTC to Fri Jul 17 12:00:00 2009 UTC. There were 6 messages: 6 from Zope Tests. Test failures ------------- Subject: FAILED (failures=1) : Zope-2.12 Python-2.6.2 : Linux From: Zope Tests Date: Thu Jul 16 20:41:53 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012075.html Subject: FAILED (failures=7) : Zope-2.12-alltests Python-2.6.2 : Linux From: Zope Tests Date: Thu Jul 16 20:43:53 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012076.html Subject: FAILED (failures=1) : Zope-trunk Python-2.6.2 : Linux From: Zope Tests Date: Thu Jul 16 20:45:53 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012077.html Subject: FAILED (failures=7) : Zope-trunk-alltests Python-2.6.2 : Linux From: Zope Tests Date: Thu Jul 16 20:47:53 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012078.html Tests passed OK --------------- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Thu Jul 16 20:37:53 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012073.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Thu Jul 16 20:39:53 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012074.html

1 0

Zope Tests: 2 OK, 4 Failed
by Zope Tests Summarizer 16 Jul '09

16 Jul '09

Summary of messages to the zope-tests list. Period Wed Jul 15 12:00:00 2009 UTC to Thu Jul 16 12:00:00 2009 UTC. There were 6 messages: 6 from Zope Tests. Test failures ------------- Subject: FAILED (failures=1) : Zope-2.12 Python-2.6.2 : Linux From: Zope Tests Date: Wed Jul 15 20:41:34 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012069.html Subject: FAILED (failures=7) : Zope-2.12-alltests Python-2.6.2 : Linux From: Zope Tests Date: Wed Jul 15 20:43:34 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012070.html Subject: FAILED (failures=1) : Zope-trunk Python-2.6.2 : Linux From: Zope Tests Date: Wed Jul 15 20:45:34 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012071.html Subject: FAILED (failures=7) : Zope-trunk-alltests Python-2.6.2 : Linux From: Zope Tests Date: Wed Jul 15 20:47:34 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012072.html Tests passed OK --------------- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Wed Jul 15 20:37:34 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012067.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Wed Jul 15 20:39:34 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-July/012068.html

1 0