April 2009 - Zope-Dev

Re: [Zope-dev] SVN: zope.traversing/trunk/ Use applySkin from new location zope.publisher.skinnable
by Tres Seaver 06 Apr '09

06 Apr '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Roger Ineichen wrote: > Log message for revision 97754: > Use applySkin from new location zope.publisher.skinnable > instead of zope.publisher.browser. > > Changed: > U zope.traversing/trunk/CHANGES.txt > U zope.traversing/trunk/src/zope/traversing/namespace.py > > -=- > Modified: zope.traversing/trunk/CHANGES.txt > =================================================================== > --- zope.traversing/trunk/CHANGES.txt 2009-03-10 01:19:59 UTC (rev 97753) > +++ zope.traversing/trunk/CHANGES.txt 2009-03-10 01:23:10 UTC (rev 97754) > @@ -5,6 +5,9 @@ > 3.5.3 (unreleased) > ------------------ > > +- Use applySkin from new location. zope.publisher.skinnable instead of > + zope.publisher.browser. > + > - Use IAbsoluteURL lookup instead of the "absolute_url" view in the > recursive AbsoluteURL adapters (LP: #338101). > > > Modified: zope.traversing/trunk/src/zope/traversing/namespace.py > =================================================================== > --- zope.traversing/trunk/src/zope/traversing/namespace.py 2009-03-10 01:19:59 UTC (rev 97753) > +++ zope.traversing/trunk/src/zope/traversing/namespace.py 2009-03-10 01:23:10 UTC (rev 97754) > @@ -26,7 +26,7 @@ > from zope.interface import providedBy, directlyProvides, directlyProvidedBy > from zope.location.interfaces import IRoot, LocationError > from zope.publisher.interfaces.browser import IBrowserSkinType > -from zope.publisher.browser import applySkin > +from zope.publisher.skinnable import applySkin > from zope.security.proxy import removeSecurityProxy > from zope.traversing.interfaces import ITraversable, IPathAdapter This change breaks older packages who might expect a 3.5.x version to have compatible dependencies: it impliictly requires zope.component>=3.6.0, which is wildly incompatible. I think the 3.5.3 release tag should be copied as 3.6.0, and a 3.5.4 should be released which reverts this change. 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 iD8DBQFJ2NWd+gerLs4ltQ4RAjXYAJ41DrNdU21xBtWftCsRy1t3yM87UQCfQrb4 erQC8Q/T3tlTa5Tv5TsC+Jw= =/bXG -----END PGP SIGNATURE-----

2 2

z3c.pt bug
by Roger Ineichen 06 Apr '09

06 Apr '09

Hi Malthe I just improved coverage in z3c.form and found a bug in z3c.pt. Can you run the group.txt tests in z3c.form and confirm the issue. A div tag get skipped after some nested repeat tags. (line 898, in group.txt) Is this a known issue? Can you fix this or give me some hints which let me do this? Regards Roger Ineichen _____________________________ END OF MESSAGE

2 4

Zope Tests: 7 OK, 1 Failed
by Zope Tests Summarizer 06 Apr '09

06 Apr '09

Summary of messages to the zope-tests list. Period Sun Apr 5 12:00:00 2009 UTC to Mon Apr 6 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Test failures ------------- Subject: FAILED (failures=2, errors=1) : Zope-trunk-alltests Python-2.6.1 : Linux From: Zope Tests Date: Sun Apr 5 21:00:03 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011402.html Tests passed OK --------------- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Sun Apr 5 20:45:52 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011395.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Sun Apr 5 20:48:00 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011396.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Sun Apr 5 20:50:01 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011397.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Sun Apr 5 20:52:01 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011398.html Subject: OK : Zope-trunk Python-2.6.1 : Linux From: Zope Tests Date: Sun Apr 5 20:54:02 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011399.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Sun Apr 5 20:56:02 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011400.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Sun Apr 5 20:58:03 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011401.html

1 0

chameleon.zpt: broken html output?
by Christian Theune 06 Apr '09

06 Apr '09

Hi, for some reason chameleon.zpt gives the following output: <html> <head> ... </head></html>head> <body> ... </body>/html> The template seems fine, anybody seen that before? 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 7 · fax +49 345 1229889 1 Zope and Plone consulting and development

3 2

z3c.form - status of 1.9.0 and 2.0 (and a bug)
by Martin Aspeli 06 Apr '09

06 Apr '09

Hi, Today, I found a bug in ChoiceTerms: it will only bind the field if field.vocabulary is None, which breaks uses of an IContextSourceBinder. I thought to fix that in svn, but there's no 1.9.x branch, and 2.0 (trunk) is a very different beast. Tracking 2.0 trunk is not an option right now. I couldn't even get Zope to start up with 2.0 trunk, which is depending on lots of 3.5.x packages that I can't get to work with Zope. So, for now, I've made do with a monkey patch, but that's obviously not ideal. So: - When will we see a 2.0 release? I asked that question months ago, but I'm not sure if we're any closer? - What do we do with the 1.9.x line? Cheers, Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book

3 3

Constant values defined in interfaces
by Chris Rossi 05 Apr '09

05 Apr '09

Hello, I was wondering if the Zope collective had given any consideration to allowing constants to be defined in interfaces. To be clear, these are constant values that make up the protocol defined by the interface. Just to have a concrete example, let's say we're modeling an http response: class IHttpResponse(Interface): """Models an HTTP 1.1 response. """ status = Attribute("HTTP status code for this response.") It might be useful to include in our interface spec what some proper values for status code might be and make them available to applications as static constants on the interface class. A naive implementer might do something like this: class IHttpResponse(Interface): """Models an HTTP 1.1 response. """ HTTP_OK = "200 Ok" HTTP_NOT_FOUND = "404 Not Found" status = Attribute("HTTP status code for this response.") As you can see, the HTTP_OK and HTTP_NOT_FOUND constants are conceptually part of the interface--they help define our contract for http responses. We might expect to then be able to do something like this in application code: response.status = IHttpResponse.HTTP_OK Of course, if you try this currently, Interface will complain: InvalidInterface: Concrete attribute, HTTP_OK I did do some poking around in the source code and in the documentation, such as it is, and didn't see anything like constants in interfaces, but it's possible this use case has already been addressed somehow and I am just ignorant of how, in which case, my apologies, and thanks for telling me the already accepted way to do this. If this hasn't been done yet, I can envision doing something like: from zope.interface import Constant class IHttpResponse(Interface): """Models an HTTP 1.1 response. """ HTTP_OK = Constant("200 Ok", "An HTTP Ok response.") HTTP_NOT_FOUND = Constant("404 Not Found", "An HTTP Not Found response") status = Attribute("HTTP status code for this response.") Using descriptors, the results could be both static and immutable. Does this seem useful to anyone besides me? Anyone who's done much Java programming will recognize that I did not have an original idea here. If there is a general buy in, I would be happy to attempt an implementation and submit a patch. Thanks, Chris PS I did find a hack that will let you accomplish this, although it is a hack rather than a supported feature of the component architecture: class IHttpResponse(Interface): """Models an HTTP 1.1 response. """ status = Attribute("HTTP status code for this response.") IHttpResponse.HTTP_OK = "200 Ok" IHttpResponse.HTTP_NOT_FOUND = "404 Not Found" Because the interface class is decorated after the type is instantiated, the InvalidInterface check is avoided.

7 12

Zope Tests: 7 OK, 1 Failed
by Zope Tests Summarizer 05 Apr '09

05 Apr '09

Summary of messages to the zope-tests list. Period Sat Apr 4 12:00:00 2009 UTC to Sun Apr 5 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Test failures ------------- Subject: FAILED (failures=2, errors=1) : Zope-trunk-alltests Python-2.6.1 : Linux From: Zope Tests Date: Sat Apr 4 20:56:28 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011394.html Tests passed OK --------------- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Sat Apr 4 20:42:22 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011387.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Sat Apr 4 20:44:26 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011388.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Sat Apr 4 20:46:26 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011389.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Sat Apr 4 20:48:26 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011390.html Subject: OK : Zope-trunk Python-2.6.1 : Linux From: Zope Tests Date: Sat Apr 4 20:50:27 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011391.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Sat Apr 4 20:52:27 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011392.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Sat Apr 4 20:54:27 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011393.html

1 0

[Fwd: [Bug 343079] [NEW] Broken distribution (2009-03-15)]
by Tres Seaver 05 Apr '09

05 Apr '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - -------- Original Message -------- Subject: [Bug 343079] [NEW] Broken distribution (2009-03-15) Date: Sun, 15 Mar 2009 07:42:00 -0000 From: dmaurer <dieter(a)handshake.de> Reply-To: Bug 343079 <343079(a)bugs.launchpad.net> To: tseaver(a)palladion.com References: <20090315074200.12457.19313.malonedeb(a)potassium.ubuntu.com> Public bug reported: The current (2009-03-12) PyPI distribution for Zope2 2.12.0a1 is broken. 'easy_install'ing it leads to version conflicts for 'zope.component' (3.5.1 versus 3.6.0) in the call of 'mkzopeinstance'. ** Affects: zope2 Importance: Undecided Status: New The breakage is due to the release of the new zope.prinipalregistry egg. We should probably manage a Zope2 indes and tell people to use it when running easy_install, because PyPI is not suitable for the task given setuptools' "incremental requirements discovery" design. 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 iD8DBQFJvT4A+gerLs4ltQ4RAo0LAJ4q83+Ua0hEQUb5ecOhU8IufTcXnQCfV9wd 6eFVN+pmQTi0CW+ki8f+f8M= =zsxY -----END PGP SIGNATURE-----

5 16

zope.testing.runner: protecting against rogue threads
by Christian Theune 05 Apr '09

05 Apr '09

Hi, if tests spawn non-daemon threads, then the test runner can get stuck. The easiest way that I see is to always --exit-with-status and to make --exist-with-status also call sys.exit() when the tests passed. Any objections? 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 7 · fax +49 345 1229889 1 Zope and Plone consulting and development

3 5

Zope Tests: 6 OK, 2 Failed
by Zope Tests Summarizer 04 Apr '09

04 Apr '09

Summary of messages to the zope-tests list. Period Fri Apr 3 12:00:00 2009 UTC to Sat Apr 4 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Test failures ------------- Subject: FAILED (failures=1) : Zope-trunk Python-2.6.1 : Linux From: Zope Tests Date: Fri Apr 3 20:53:14 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011383.html Subject: FAILED (failures=3, errors=1) : Zope-trunk-alltests Python-2.6.1 : Linux From: Zope Tests Date: Fri Apr 3 20:59:15 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011386.html Tests passed OK --------------- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Fri Apr 3 20:45:09 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011379.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Fri Apr 3 20:47:10 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011380.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Fri Apr 3 20:49:10 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011381.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Fri Apr 3 20:51:11 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011382.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Fri Apr 3 20:55:14 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011384.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Fri Apr 3 20:57:15 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011385.html

1 0