- Zope-Dev - Zope lists

Zope Tests: 6 OK
by Zope Tests Summarizer 06 Jan '10

06 Jan '10

Summary of messages to the zope-tests list. Period Tue Jan 5 12:00:00 2010 UTC to Wed Jan 6 12:00:00 2010 UTC. There were 6 messages: 6 from Zope Tests. Tests passed OK --------------- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Tue Jan 5 20:37:03 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013329.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Tue Jan 5 20:39:03 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013330.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Tue Jan 5 20:41:03 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013331.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Tue Jan 5 20:43:04 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013332.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Tue Jan 5 20:45:04 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013333.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Tue Jan 5 20:47:04 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013334.html

1 0

Where best to intercept a request to send a 304 response in Zope 2
by Martin Aspeli 06 Jan '10

06 Jan '10

Hi, A few of us are playing with some caching tools, trying to get to a more sane and less monkey patch-laden approach than CacheFu (Products.CacheSetup), for use with Zope 2.12. It is relatively easy to set response headers, e.g. in an IPubBeforeCommit event handler. However, we also need to be able to intercept a request to send a 304 response if the underlying object has not been modified. CacheFu monkey patches ZPT rendering to avoid the actual rendering if a 304 response is being sent, returning an empty string instead. I'd rather not have such patches, though, and anyway this only work with things rendered as ZPTs. It also doesn't avoid any pre-work that a view may do before rendering its template, if indeed it has one. Another thought was to use IPubAfterTraversal, at which point we have the object to publish and security checks have been completed. However, ZPublisher.Publish goes straight from that into mapply(). Can anyone think of a good way to do this? Maybe we need to add some kind of condition around mapply(), e.g. to do not nothing if there's a 304 response header, or some other marker? Cheers, Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book

3 4

zope.publisher 3.12 broke 25 zope.app packages
by Martijn Faassen 06 Jan '10

06 Jan '10

Hi there, 25 zope.app packages are broken due to changes in zope.publisher 3.12. zope.publisher had some components factored out of it into zope.login. I fixed zope.app.exception: it could be fixed by adding the zope.login requirement and adding a zcml include statement. I suspect most, probably all, other failures are similarly shallow. The breaking of so many packages wasn't noticed by anyone, until tests of svn checkouts that previously worked now broke. I hope we can put mechanisms in place so that developers of ZTK packages can be better made aware of breaking other packages that depend on the ZTK. This way the developer making the changes could do one or more of the following: * provide better backward compatibility * fix up the breaking packages * provide a better warning to others who are maintaining these packages that something was broken. I faintly, faintly recall we had such early-warning mechanisms in the past. :) Regards, Martijn

4 5

new zope.schema and zope.configuration releases
by Chris McDonough 06 Jan '10

06 Jan '10

FYI, I just made two new releases: zope.schema 3.6.1 zope.configuration 3.7.1 These releases provide basic compatibility with Jython. - C

2 1

Re: [Zope-dev] SVN: Zope/branches/2.12/ Fixed possible TypeError while sending multipart emails.
by Tres Seaver 06 Jan '10

06 Jan '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Maurits van Rees wrote: > Log message for revision 107689: > Fixed possible TypeError while sending multipart emails. > > Changed: > U Zope/branches/2.12/doc/CHANGES.rst > U Zope/branches/2.12/src/Products/MailHost/MailHost.py > U Zope/branches/2.12/src/Products/MailHost/tests/testMailHost.py Is this fix already on the trunk? Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver(a)palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAktD3VkACgkQ+gerLs4ltQ72+gCgrCjbpo5s6gAHG3EFXvwGfnuD vO4AoMQKbAyIoz8YG3LAgy6T78Z1AaG0 =WV5M -----END PGP SIGNATURE-----

1 1

Re: [Zope-dev] SVN: five.pt/trunk/ Fixed a calling convention oddity.
by Tres Seaver 06 Jan '10

06 Jan '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Malthe Borch wrote: > Log message for revision 107710: > Fixed a calling convention oddity. > > Changed: > U five.pt/trunk/CHANGES.txt > U five.pt/trunk/src/five/pt/patches.py > > -=- <snip> > Modified: five.pt/trunk/src/five/pt/patches.py > =================================================================== > --- five.pt/trunk/src/five/pt/patches.py 2010-01-05 15:50:46 UTC (rev 107709) > +++ five.pt/trunk/src/five/pt/patches.py 2010-01-05 16:32:23 UTC (rev 107710) > @@ -26,7 +26,7 @@ > except ImportError: > from zope.app.pagetemplate.viewpagetemplatefile import BoundPageTemplate > import Acquisition > - > + > class BoundPageTemplate(BoundPageTemplate, Acquisition.Implicit): > """Implementing Acquisition.interfaces.IAcquirer and > IAcquisitionWrapper. > @@ -34,9 +34,9 @@ > > __parent__ = property(lambda self: self.im_self) > > - def __call__(self, *args, **kw): > + def __call__(self, im_self=None, *args, **kw): > if self.im_self is None: > - im_self, args = args[0], args[1:] > + im_self = im_self > else: > im_self = aq_base(self.im_self) > if IAcquirer.providedBy(im_self): <snip> That can't be right: the if clause is a no-op. And no test for the case which was broken? Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver(a)palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAktD3igACgkQ+gerLs4ltQ7TZACeMO8fPNvRL10ySynw2ALSP9KF dpkAni7rXfeg6Xg+FzK1c+kPNpj1RkGN =n5Zm -----END PGP SIGNATURE-----

1 0

zope.security dependency on zope.exceptions
by Fabio Tranchitella 06 Jan '10

06 Jan '10

Happy New Year to everybody, I'm working to isolate a core set of ZTK packages which are independent from Zope and reusable outside the Zope community. One of them is zope.security, which can be used (and it is useful, indeed) with non-zope frameworks too. While doing it, I'm trying to remove dependencies which are zope-specific, to minimize the overhead for developers who are using the whole zope stack (like me :)). zope.security depends on zope.exceptions because it imports this symbol in zope.security.checker: from zope.exceptions import DuplicationError zope.exceptions defines DuplicationError as: class IDuplicationError(Interface): pass class DuplicationError(Exception): """A duplicate registration was attempted""" implements(IDuplicationError) The zope.exceptions package contains "exception interfaces and implementations which are so general purpose that they don't belong in Zope application-specific packages.", as stated by the README. I propose to make the remove the dependency between zope.security and zope.exceptions with a conditional import: * if zope.exceptions is available, use DuplicationError from it; * if it is not available, define a zope.security-specific DuplicationError (which inherits from ValueError, maybe). As using zope.exceptions only make sense if you are checking the exception type importing its interface from the zope.exceptions package, and thus depending on it, I see no risk in such a change. Thoughts? Comments? Fabio

2 2

shrinking the ZTK: a proposed solution
by Martijn Faassen 06 Jan '10

06 Jan '10

Hi there, So here's my proposed solution for the ZTK shrinking issue: The ZTK branch 'faassen-smaller' contains Hanno's smaller ZTK. Since Zope 2 forked the ZTK in response and continued to make changes to their fork, I've tried to keep it in sync with the Zope 2 fork. I've created a new 'zopeapp' package that expands the ZTK with zope.app. packages in my sandbox. This extracts that information from the ZTK. Hopefully after we get some feedback from other steering group members (very silent indeed in the holiday period when all this happened) we can make these two projects the official one: a ZTK project and a zopeapp project. A few things I ask the ZTK maintainers: I ask the ZTK maintainers to have the same concern for the zope.app packages as for any other user of the ZTK: work to support zopeapp's compatibility with the ZTK. If the zopeapp maintainers have issues, listen to them seriously. I think everybody can agree that this is within the ZTK mandate for the time being, as zopeapp clearly exists and is being used by a significant amount of people. (I'd like to work to retire it by making it used by far less people) I also strongly encourage the ZTK maintainers to consider the situation of backwards compatibility seriously. Help people transition from their code now to the ZTK. Helping everybody migrate to the ZTK smoothly increases the value of the ZTK itself. Obviously I cannot *force* ZTK maintainers to worry about this. Instead I'm appealing to your self-interest. And of course the transition burden is shared and should not fall solely or even predominantly on the ZTK maintainers. I also think we as ZTK maintainers should better consider the concerns of other users of the ZTK. In this case, Zope 2 had less of a concern for zope.app than Grok or Zope 3. I didn't even understand this until the debate was further along. The concerns of others should be considered as well instead of simply rejected. We usually can find ways to balance the concerns of everybody. To that end concerns (or lack thereof) should be clearly communicated and be listened to. Regards, Martijn

11 30

Zope Tests: 3 OK, 3 Unknown
by Zope Tests Summarizer 05 Jan '10

05 Jan '10

Summary of messages to the zope-tests list. Period Mon Jan 4 12:00:00 2010 UTC to Tue Jan 5 12:00:00 2010 UTC. There were 6 messages: 6 from Zope Tests. Unknown ------- Subject: UNKNOWN : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Mon Jan 4 20:45:19 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013325.html Subject: UNKNOWN : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Mon Jan 4 20:47:19 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013326.html Subject: UNKNOWN : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Mon Jan 4 20:49:19 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013327.html Tests passed OK --------------- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Mon Jan 4 20:41:19 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013323.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Mon Jan 4 20:43:19 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013324.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Mon Jan 4 20:51:19 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013328.html

1 0

Possible Zope 2.12 regression - Five page templates use restrictedTraverse for TAL
by Martin Aspeli 05 Jan '10

05 Jan '10

Hi, Ages ago, I started a thread (I think on this list) about the use of TAL expression in Zope 3-style page templates (i.e. ViewPageTemplateFile's used on views) incorrectly performing security checks when using TAL expressions. I think Tres fixed it at the time (I can't find the original mail), but in Zope 2.12.2 there seems to have been a regression. I'd like to make sure I've not missed something, though. I see the problem in Plone 4.0a2 on Zope 2.12, trying to use plone.app.registry. This package has a class that derives from plone.registry.registry.Registry (a "ZTK-only" version) and SimpleItem (to get Zope 2 security and ZMI visibility). Otherwise, it does nothing. There is a view for this class registered like this: <browser:page name="view" for="plone.registry.interfaces.IRegistry" template="records.pt" permission="cmf.ManagePortal" /> In records.pt, there is the following: <tr tal:repeat="record context/records/values"> ... </tr> This fails with the stack trace below. However, if I change it to use a python: expression, it's all fine: <tr tal:repeat="record python:context.records.values()"> ... </tr> As you can see from the stack trace, the TAL expression has resulted in the use of restrictedTraverse(). I think it should be using unrestrictedTraverse(), since ViewPageTemplateFile's are filesystem code. (In this particular case, it's failing the restrictedTraverse check because 'records' is a property and so doesn't have an aq chain, but nevermind that). Stack trace: 2009-12-13 00:40:13 ERROR Zope.SiteErrorLog 1260636013.580.4115611559 http://localhost:8080/test/portal_registry/@@view Traceback (innermost last): Module ZPublisher.Publish, line 127, in publish Module ZPublisher.mapply, line 77, in mapply Module Products.PDBDebugMode.runcall, line 70, in pdb_runcall Module ZPublisher.Publish, line 47, in call_object Module Products.Five.browser.metaconfigure, line 427, in __call__ Module Products.Five.browser.pagetemplatefile, line 126, in __call__ Module Products.Five.browser.pagetemplatefile, line 60, in __call__ Module zope.pagetemplate.pagetemplate, line 115, in pt_render Module zope.tal.talinterpreter, line 271, in __call__ Module zope.tal.talinterpreter, line 343, in interpret Module zope.tal.talinterpreter, line 888, in do_useMacro Module zope.tal.talinterpreter, line 343, in interpret Module zope.tal.talinterpreter, line 533, in do_optTag_tal Module zope.tal.talinterpreter, line 518, in do_optTag Module zope.tal.talinterpreter, line 513, in no_tag Module zope.tal.talinterpreter, line 343, in interpret Module zope.tal.talinterpreter, line 888, in do_useMacro Module zope.tal.talinterpreter, line 343, in interpret Module zope.tal.talinterpreter, line 533, in do_optTag_tal Module zope.tal.talinterpreter, line 518, in do_optTag Module zope.tal.talinterpreter, line 513, in no_tag Module zope.tal.talinterpreter, line 343, in interpret Module zope.tal.talinterpreter, line 946, in do_defineSlot Module zope.tal.talinterpreter, line 343, in interpret Module zope.tal.talinterpreter, line 533, in do_optTag_tal Module zope.tal.talinterpreter, line 518, in do_optTag Module zope.tal.talinterpreter, line 513, in no_tag Module zope.tal.talinterpreter, line 343, in interpret Module zope.tal.talinterpreter, line 954, in do_defineSlot Module zope.tal.talinterpreter, line 343, in interpret Module zope.tal.talinterpreter, line 533, in do_optTag_tal Module zope.tal.talinterpreter, line 518, in do_optTag Module zope.tal.talinterpreter, line 513, in no_tag Module zope.tal.talinterpreter, line 343, in interpret Module zope.tal.talinterpreter, line 946, in do_defineSlot Module zope.tal.talinterpreter, line 343, in interpret Module zope.tal.talinterpreter, line 819, in do_loop_tal Module zope.tales.tales, line 682, in setRepeat Module zope.tales.tales, line 696, in evaluate - URL: /Users/optilude/Development/Plone/Instances/Clients/Lotterywest/osc/src/plone.app.registry/plone/app/registry/browser/records.pt - Line 33, Column 12 - Expression: <PathExpr standard:u'context/records/values'> - Names: {'args': (), 'container': <Registry at /test/portal_registry>, 'context': <Registry at /test/portal_registry>, 'default': <object object at 0x1002c7b50>, 'here': <Registry at /test/portal_registry>, 'loop': {}, 'nothing': None, 'options': {}, 'repeat': <Products.PageTemplates.Expressions.SafeMapping object at 0x108e8b3b0>, 'request': <HTTPRequest, URL=http://localhost:8080/test/portal_registry/@@view>, 'root': <Application at >, 'template': <Products.Five.browser.pagetemplatefile.ViewPageTemplateFile object at 0x10792b950>, 'traverse_subpath': [], 'user': <PropertiedUser 'admin'>, 'view': <Products.Five.metaclass.SimpleViewClass from /Users/optilude/Development/Plone/Instances/Clients/Lotterywest/osc/src/plone.app.registry/plone/app/registry/browser/records.pt object at 0x10885c810>, 'views': <Products.Five.browser.pagetemplatefile.ViewMapper object at 0x108cbb0d0>} Module zope.tales.expressions, line 217, in __call__ Module Products.PageTemplates.Expressions, line 127, in _eval Module zope.tales.expressions, line 124, in _eval Module Products.PageTemplates.Expressions, line 76, in boboAwareZopeTraverse Module OFS.Traversable, line 312, in restrictedTraverse Module OFS.Traversable, line 247, in unrestrictedTraverse - __traceback_info__: ([], 'records') Unauthorized: You are not allowed to access 'records' in this context > /Users/optilude/.buildout/eggs/Zope2-2.12.1-py2.6-macosx-10.6-i386.egg/OFS/Traversable.py(247)unrestrictedTraverse() Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book

3 7