July 2009 - Zope-Dev

zope.release's bin/upload
by Marius Gedminas 15 Jul '09

15 Jul '09

Consider this: $ svn info | grep URL URL: svn+ssh://svn.zope.org/repos/main/zope.release/branches/3.4 $ bin/buildout ... $ bin/upload str(object) -> string Return a nice string representation of the object. If the argument is a string, the return value is the same object. Can somebody explain to me what's happening here? Marius Gedminas -- http://pov.lt/ -- Zope 3 consulting and development

1 0

utilities and python version in zope2.12
by Jonas Meurer 15 Jul '09

15 Jul '09

Hello, I just recognized that lots of utilities in zope2.12 still do have python2.4 as interpreter while the release notes of zope2.12 talk about python2.5 and python2.6 being the only supported python versions. greetings, jonas

3 7

zope.testing 3.7.7 released
by Christian Theune 15 Jul '09

15 Jul '09

Hi, I just released zope.testing 3.7.7. It contains two interesting changes: - The test runner now correctly does *not* descend into `test-path`s which are not Python packages. This solves an issue with eggs being picked up when run from buildout directories which both contained the develop egg without an additional source directory and the egg directory. - The code for using zope.exceptions exception formatters was handled incompletely and very ad-hoc. The dependency was folded from an extra into a direct dependency and the formatters are now used per default and work for doctests as well. This should make debugging page template issues (e.g. with the testbrowser) a lot easier. Cheers, Christian -- Christian Theune · ct(a)gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development

2 1

test setup layer sorting
by Reinout van Rees 14 Jul '09

14 Jul '09

zope/testing/testrunner/runner.py's order_by_bases() function orders layers by inheritance, basically. So if you've got a FunctionalTestLayer that inherits from some BasicTestLayer, the tests that use the basic test layer will be executed before the functional test layer ones. If there's no inheritance, the layers are sorted by name. Quite sane. Problem: I use grok. Which does some magic that probably throws off the code coverage reports. Quite some code appears untested, even though I *do* test it. The problem disappears if just import the python module first in some basic test before the grokking happened. I use z3c.testsetup: - My basic doctests end up on the zope.testing.testrunner.layer.UnitTests layer. - My functional doctests on the z3c.testsetup.functional.layer.DefaultZCMLLayer layer which inherits from zope.app.testing's ZCMLLayer. - zope.app.testing's ZCMLLayer does not inherit from anything, so also not from zope.testing's unittest layer. - 'zope....' is alphabetically behind 'z3c.testsetup....', so the functional layer is sorted in front of the basic unittest one. - So my grokked code appears untested. What's the best solution? Should zope.app.testing's ZCMLLayer inherit from zope.testing's UnitTests layer? Should z3c.testsetup do some inheriting of its own? Reinout -- Reinout van Rees - reinout(a)vanrees.org - http://reinout.vanrees.org Software developer at http://www.thehealthagency.com "Military engineers build missiles. Civil engineers build targets"

4 7

z3c.form: data manager for PersistentDict/PersistentMapping
by Michael Howitz 14 Jul '09

14 Jul '09

Hello, z3c.form.datamanager.DictionaryField is a data manager which is registered for fields on a dict. In its __init__ it checks whether the data object is an instance of dict. So this data manager does neither work for UserDict nor PersistentDict/PersistentMapping. I'd like to change this but there are two possibilities and I'm not sure which is the best one: 1.) Add a subclasses of DictionaryField which is registered for UserDict and which checks whether the data object is an instance of UserDict. (PersistentDict and PersistentMapping are subclasses of UserDict.) 2.) Register DictionaryField for zope.interface.common.mapping.IMapping. This might have a problem as neither UserDict nor PersistentDict/PersistentMapping seem to provide this interface. (Why?) Any suggestions? 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

3 5

Creating new five.* package
by Thomas Lotze 13 Jul '09

13 Jul '09

We've started a new package, five.hashedresource, that is supposed to integrate z3c.hashedresource into Zope2. Just to make sure not to step on someone's toes: is it OK to just create such a package in that namespace? -- Thomas

2 1

Re: [Zope-dev] SVN: Zope/branches/2.12/ Correctly handle unauthorized exceptions in the ZPublisherExceptionHook.
by Tres Seaver 10 Jul '09

10 Jul '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hanno Schlichting wrote: > Log message for revision 101181: > Correctly handle unauthorized exceptions in the ZPublisherExceptionHook. > > Modified: Zope/branches/2.12/src/Zope2/App/startup.py > =================================================================== > --- Zope/branches/2.12/src/Zope2/App/startup.py 2009-06-20 19:53:08 UTC (rev 101180) > +++ Zope/branches/2.12/src/Zope2/App/startup.py 2009-06-21 00:00:53 UTC (rev 101181) > @@ -24,6 +24,7 @@ > from time import asctime > from types import StringType, ListType > from zExceptions import Redirect > +from zExceptions import Unauthorized > from ZODB.POSException import ConflictError > import transaction > import AccessControl.User > @@ -170,7 +171,7 @@ > if t.lower() in ('unauthorized', 'redirect'): > raise > else: > - if t is SystemExit or t is Redirect: > + if t is SystemExit or t is Redirect or t is Unauthorized: > raise > > if issubclass(t, ConflictError): What is the motivation here? Zope2 applications have hooked Unauthorized exceptions *forever*: - You can see them in the error_log (if you take them out of the ignore list). This change (the fixed version) breaks unit tests which assert that the exception can be hooked: - -------------------------------------------------------------------------- $ bin/test -s Zope2.App Running zope.testing.testrunner.layer.UnitTests tests: Set up zope.testing.testrunner.layer.UnitTests in 0.000 seconds. Error in test testRenderUnauthorizedBrokenClient (Zope2.App.tests.testExceptionHook.ExceptionMessageRenderTest) Traceback (most recent call last): File "/home/tseaver/projects/Zope-CVS/lib/python2.6/unittest.py", line 279, in run testMethod() File "/home/tseaver/projects/Zope-CVS/Zope-trunk/src/Zope2/App/tests/testExceptionHook.py", line 284, in testRenderUnauthorizedBrokenClient self.assertRaises(AttributeError, self.call, client, request, f) File "/home/tseaver/projects/Zope-CVS/lib/python2.6/unittest.py", line 336, in failUnlessRaises callableObj(*args, **kwargs) File "/home/tseaver/projects/Zope-CVS/Zope-trunk/src/Zope2/App/tests/testExceptionHook.py", line 74, in call sys.exc_info()[2], File "/home/tseaver/projects/Zope-CVS/Zope-trunk/src/Zope2/App/tests/testExceptionHook.py", line 69, in call f(*args, **kw) File "/home/tseaver/projects/Zope-CVS/Zope-trunk/src/Zope2/App/tests/testExceptionHook.py", line 281, in f raise Unauthorized, 1 Unauthorized: You are not allowed to access '1' in this context Error in test testRenderUnauthorizedOldClient (Zope2.App.tests.testExceptionHook.ExceptionMessageRenderTest) Traceback (most recent call last): File "/home/tseaver/projects/Zope-CVS/lib/python2.6/unittest.py", line 279, in run testMethod() File "/home/tseaver/projects/Zope-CVS/Zope-trunk/src/Zope2/App/tests/testExceptionHook.py", line 251, in testRenderUnauthorizedOldClient self.call(client, request, f) File "/home/tseaver/projects/Zope-CVS/Zope-trunk/src/Zope2/App/tests/testExceptionHook.py", line 74, in call sys.exc_info()[2], File "/home/tseaver/projects/Zope-CVS/Zope-trunk/src/Zope2/App/tests/testExceptionHook.py", line 69, in call f(*args, **kw) File "/home/tseaver/projects/Zope-CVS/Zope-trunk/src/Zope2/App/tests/testExceptionHook.py", line 248, in f raise Unauthorized, 1 Unauthorized: You are not allowed to access '1' in this context Error in test testRenderUnauthorizedStandardClient (Zope2.App.tests.testExceptionHook.ExceptionMessageRenderTest) Traceback (most recent call last): File "/home/tseaver/projects/Zope-CVS/lib/python2.6/unittest.py", line 279, in run testMethod() File "/home/tseaver/projects/Zope-CVS/Zope-trunk/src/Zope2/App/tests/testExceptionHook.py", line 262, in testRenderUnauthorizedStandardClient self.call(client, request, f) File "/home/tseaver/projects/Zope-CVS/Zope-trunk/src/Zope2/App/tests/testExceptionHook.py", line 74, in call sys.exc_info()[2], File "/home/tseaver/projects/Zope-CVS/Zope-trunk/src/Zope2/App/tests/testExceptionHook.py", line 69, in call f(*args, **kw) File "/home/tseaver/projects/Zope-CVS/Zope-trunk/src/Zope2/App/tests/testExceptionHook.py", line 259, in f raise Unauthorized, 1 Unauthorized: You are not allowed to access '1' in this context Error in test testRenderUnauthorizedStandardClientMethod (Zope2.App.tests.testExceptionHook.ExceptionMessageRenderTest) Traceback (most recent call last): File "/home/tseaver/projects/Zope-CVS/lib/python2.6/unittest.py", line 279, in run testMethod() File "/home/tseaver/projects/Zope-CVS/Zope-trunk/src/Zope2/App/tests/testExceptionHook.py", line 273, in testRenderUnauthorizedStandardClientMethod self.call(client.dummyMethod, request, f) File "/home/tseaver/projects/Zope-CVS/Zope-trunk/src/Zope2/App/tests/testExceptionHook.py", line 74, in call sys.exc_info()[2], File "/home/tseaver/projects/Zope-CVS/Zope-trunk/src/Zope2/App/tests/testExceptionHook.py", line 69, in call f(*args, **kw) File "/home/tseaver/projects/Zope-CVS/Zope-trunk/src/Zope2/App/tests/testExceptionHook.py", line 270, in f raise Unauthorized, 1 Unauthorized: You are not allowed to access '1' in this context Failure in test testCustomExceptionViewUnauthorized (Zope2.App.tests.testExceptionHook.ExceptionViewsTest) Traceback (most recent call last): File "/home/tseaver/projects/Zope-CVS/lib/python2.6/unittest.py", line 279, in run testMethod() File "/home/tseaver/projects/Zope-CVS/Zope-trunk/src/Zope2/App/tests/testExceptionHook.py", line 353, in testCustomExceptionViewUnauthorized self.failUnless(isinstance(v, HTTPResponse), v) File "/home/tseaver/projects/Zope-CVS/lib/python2.6/unittest.py", line 325, in failUnless if not expr: raise self.failureException, msg AssertionError: You are not allowed to access '1' in this context Ran 23 tests with 1 failures and 4 errors in 0.512 seconds. Tearing down left over layers: Tear down zope.testing.testrunner.layer.UnitTests in 0.000 seconds. - -------------------------------------------------------------------------- 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.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFKT5lk+gerLs4ltQ4RAuXKAJ4x+m289pMfGeYprwdJgAJ/6RkIBACdG8FO VYiQVeOKXbGSQ/g65GkP0sw= =RH3T -----END PGP SIGNATURE-----

2 1

z3c.form pass context to multi widgets in MultiConverter
by Gerhard Weis 08 Jul '09

08 Jul '09

Hi, some widgets may require a valid context to work properly. one such widget is z3c.formquery. The attached patch passes the current widget's context to the sub widgets during data conversion in z3c.form.converter.MultiConverter. The patch handles this the same way as passing the form property is implemented. (The patch is against current trunk). Sorry, but I was not sure how to add a test for this. (However, there is also no explicit test for passing the form property). I ran the current test suite with python2.4 and it did not cause any additional issues :) . The second patch here was required on my system. It seems, that zope.app.component is a missing dependency for z3c.form. (at least for now). cheers, Gerhard ------------------------------------------------------------------------ Index: src/z3c/form/converter.py =================================================================== --- src/z3c/form/converter.py (revision 101721) +++ src/z3c/form/converter.py (working copy) @@ -359,6 +359,10 @@ #form property required by objecwidget widget.form = self.widget.form zope.interface.alsoProvides(widget, interfaces.IFormAware) + if interfaces.IContextAware.providedBy(self.widget): + # context property may be required by objectwidget + widget.context = self.widget.context + zope.interface.alsoProvides(widget, interface.IContextAware) converter = zope.component.getMultiAdapter((field, widget), interfaces.IDataConverter) @@ -377,6 +381,10 @@ #form property required by objecwidget widget.form = self.widget.form zope.interface.alsoProvides(widget, interfaces.IFormAware) + if interfaces.IContextAware.providedBy(self.widget): + # context property may be required by objectwidget + widget.context = self.widget.context + zope.interface.alsoProvides(widget, interface.IContextAware) converter = zope.component.getMultiAdapter((field, widget), interfaces.IDataConverter) ------------------------------------------------------------------------ Index: setup.py =================================================================== --- setup.py (revision 101721) +++ setup.py (working copy) @@ -84,6 +84,7 @@ 'z3c.coverage', 'z3c.template', 'zc.sourcefactory', + 'zope.app.component', 'zope.app.container', 'zope.app.i18n', 'zope.app.pagetemplate',

2 4

zope.proxy, c-extensions fallback?
by Jens W. Klein 08 Jul '09

08 Jul '09

Hi, I'am just playing with repoze.bfg in google appengine (gae) and stumbled over zope.proxy. I tried to use zodict.node.Node which depends on zope.location. zope.location depends on zope.proxy. Latter has mandatory C-extensions. Are there any plans to get rid of them as a fallback for those spezial cases like gae? For zope.interface it was possible too ... tia -- Jens W. Klein - Klein & Partner KEG - BlueDynamics Alliance

2 1

How to test changes to ZTK packages?
by Jim Fulton 07 Jul '09

07 Jul '09

I should know this, but I don't. What is the recommended way to test changes to core ZTK packages to mitigate the risk that changes affect other packages? Is there a page somewhere with instructions? I tried using using zope.release. Building the trunk of zope.release with Python 2.4 and running the tests gives lots of test import errors and test failures. (Lots of tests want to import z3c.pt.) The tests hang when I try to build and run with Python 2.6. BTW, zope.release wants lxml, which is a real pain on Mac OS X and Centos 4. Does the ZTK really need to depend on lxml? Jim -- Jim Fulton Zope Corporation

11 26