January 2010 - Zope-Dev

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

broken zope.publisher because of new content types in zope.contenttype
by Roger 04 Jan '10

04 Jan '10

Hi all Since aaron added new mimetypes e.g. application/javascript, the _implicitResult method in zope.publisher.http.py (line 794) is broken because the method checks for text/* content types if unicode is given: def _implicitResult(self, body): encoding = getCharsetUsingRequest(self._request) or 'utf-8' content_type = self.getHeader('content-type') if isinstance(body, unicode): try: if not content_type.startswith('text/'): raise ValueError( 'Unicode results must have a text content type.') except AttributeError: raise ValueError( 'Unicode results must have a text content type.') Sould we remove this basic content type check above? Or enhance the check with the new added unicode valid content types like application/javascript. btw, the RFC is just Informational which defines this changes. See: http://www.rfc-editor.org/rfc/rfc4329.txt Regards Roger Ineichen _____________________________ END OF MESSAGE

3 3

Re: [Zope-dev] upload zope.app.exception to pypi
by Jan-Wijbrand Kolman 04 Jan '10

04 Jan '10

Jan-Wijbrand Kolman <janwijbrand(a)gmail.com> wrote: > Baiju M <mbaiju(a)zeomega.com> wrote: >> $ ./bin/test >> /opt/baiju/wa/z3hello/eggs/zope.testing-3.8.6-py2.6.egg/zope/testing/ > testrunner/debug.py:23: >> DeprecationWarning: zope.testing.doctest is deprecated in favour of >> the Python standard library doctest module >> from zope.testing import doctest >> Test-module import failures: >> >> Module: zope.app.exception.browser.tests.test_unauthorized >> >> Traceback (most recent call last): >> File "/tmp/zope.app.exception/src/zope/app/exception/browser/tests/ > test_unauthorized.py", >> line 20, in <module> >> import zope.app.pagetemplate.namedtemplate >> File "/opt/baiju/wa/z3hello/eggs/zope.app.pagetemplate-3.10.0-py2.6.egg/ > zope/app/pagetemplate/namedtemplate.py", >> line 20, in <module> >> from zope.browerpage.namedtemplate import implementation >> ImportError: No module named browerpage.namedtemplate > > As it turns out, since the "release" of zope.app.exception 3.6.0 namedtemplate > has again been moved. It is now in zope.browserpage. However, zope.browserpage > is not required yet by zope.app.exception. This has been fixed now, but now I'm stumped at this error: 16:17 jw:~/project/grokdev/z.a.exception $ ./bin/test /home/jw/project/grokdev/z.a.exception/eggs/zope.testing-3.8.6-py2.5.egg/zope/ testing/testrunner/debug.py:23: DeprecationWarning: zope.testing.doctest is deprecated in favour of the Python standard library doctest module from zope.testing import doctest Running zope.app.exception.testing.AppExceptionLayer tests: Set up zope.app.exception.testing.AppExceptionLayer Traceback (most recent call last): File "/home/jw/project/grokdev/z.a.exception/eggs/zope.testing-3.8.6- py2.5.egg/zope/testing/testrunner/runner.py", line 367, in run_layer setup_layer(options, layer, setup_layers) File "/home/jw/project/grokdev/z.a.exception/eggs/zope.testing-3.8.6- py2.5.egg/zope/testing/testrunner/runner.py", line 632, in setup_layer layer.setUp() File "/home/jw/project/grokdev/z.a.exception/eggs/zope.app.testing-3.7.3- py2.5.egg/zope/app/testing/functional.py", line 337, in setUp self.config_file, product_config=self.product_config) File "/home/jw/project/grokdev/z.a.exception/eggs/zope.app.testing-3.7.3- py2.5.egg/zope/app/testing/functional.py", line 226, in __init__ setup.setUpManager() File "/home/jw/project/grokdev/z.a.exception/eggs/ zope.app.securitypolicy-3.5.1-py2.5.egg/zope/app/securitypolicy/browser/tests/ functional.py", line 26, in setUpManager functional.HTTPCaller()(grant_request, handle_errors=False) File "/home/jw/project/grokdev/z.a.exception/eggs/zope.app.testing-3.7.3- py2.5.egg/zope/app/testing/functional.py", line 743, in __call__ request = publish(request, handle_errors=handle_errors) File "/home/jw/project/grokdev/z.a.exception/eggs/zope.publisher-3.12.0- py2.5.egg/zope/publisher/publish.py", line 131, in publish obj = request.traverse(obj) File "/home/jw/project/grokdev/z.a.exception/eggs/zope.publisher-3.12.0- py2.5.egg/zope/publisher/browser.py", line 556, in traverse ob, add_steps = publication.getDefaultTraversal(self, ob) File "/home/jw/project/grokdev/z.a.exception/eggs/zope.app.publication-3.10.0- py2.5.egg/zope/app/publication/browser.py", line 36, in getDefaultTraversal return ob.browserDefault(request) Unauthorized: (<zope.browserpage.simpleviewclass.SimpleViewClass from /home/jw/ project/grokdev/z.a.exception/eggs/zope.app.securitypolicy-3.5.1-py2.5.egg/zope/ app/securitypolicy/browser/granting.pt object at 0xa6e6f8c>, 'browserDefault', 'zope.Security') I'm trying to figure out what has changed that could be related to this, but if anyone has a hint for me... regards, jw

2 4

how to help Martijn (how can we have better discussions?)
by Martijn Faassen 04 Jan '10

04 Jan '10

Hi there, A meta-discussion, how dangerous! Let's see whether it can help us improve the way we work together, though. I'll talk about how I think, from my perspective, we can improve the quality of discourse on this mailing list and be more constructive. What lowered the quality of this discussion? I think it is because various people became quite upset and annoyed. That's because I reverted Hanno's changes to the ZTK trunk. I shouldn't have done that just like that, but I needed the subsequent discussion to come up with a better solution. In the turmoil, my attempts to formulate a solution that would satisfy everybody's concerns fairly well seemed to have been overlooked a little bit. Instead we focused a lot of time on discussing bits we ironically enough actually more or less agreed about, such as the role of the ZTK. Nobody seemed to quite notice that I'm in fact in favor of a smaller ZTK, even though I said so repeatedly. That's because I'm *also* in favor of maintaining the zopeapp bits a while longer and not just throwing those away. I want an exit strategy for those bits. A transition strategy. That is a legitimate topic for this mailing list at the very least. Instead, we had endless debates about whether it was a legitimate concern for the ZTK maintainers. I'm of course still right that it is. I have wonderful and coherent reasons to support my position just like everybody else does who disagrees with me. It's not really very important anyway. We're here together on this list to work together beyond the ZTK itself. So how can we have better discussions? We can have better discussions by helping me. How can you help me? Of course it helps if you agree with me. I realize that's frequently infeasible, but I certainly wouldn't mind. :) If you disagree with me, I'd like you to try to understand my concerns as much as you possibly can. In addition, try acknowledge my concerns as much as you possibly can without feeling you're lying. This works beter than just rejecting them. How else can you help me? You can propose realistic solutions for how we as a community can take care of these concerns that I have. And still fulfill your concerns at the same time. Such solutions were entirely possible in this discussion. Constructive debating is an art I'm still learning, but I had the feeling people enjoyed the rest of the debate too much to be very constructive this time... Of course the way you'd help me is the way anybody would be helped in a discussion, as the discussion becomes more constructive. Again, I know as much to blame as anyone else. I helped spark it due to my revert and my continued insistence that I am right. The revert shouldn't have happened. But I didn't know that at the time as I hadn't had time to think yet either. So how else can you help me? Give me some space to think. I believe my concerns could have been easily taken care of if we'd stopped and talked for a little bit *before* drastic changes were checked in. So, you can help me by discussing things that you know are drastic changes before you do them. I know we have had a lot of problems reaching conclusions in such discussions in the past, but we can't learn how to do better at that if we don't. And we are going to do better if I can help it. Regards, Martijn

2 3

[Announce] BlueBream: Script to setup a Zope project directory
by Baiju M 04 Jan '10

04 Jan '10

Hi All, I started a project named "BlueBream" to create a script to setup a Zope project directory. BlueBream use ZTK with some additional packages. BlueBream is based on PasteScript's template plugin. The package is available from PyPI: http://pypi.python.org/pypi/bluebream Source code is available from my Sandbox: svn://svn.zope.org/repos/main/Sandbox/baijum/bluebream/trunk Looking for your feedback. Regards, Baiju M

4 8