April 2009 - Zope-Dev

Zope Tests: 8 OK
by Zope Tests Summarizer 30 Apr '09

30 Apr '09

Summary of messages to the zope-tests list. Period Wed Apr 29 12:00:00 2009 UTC to Thu Apr 30 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Tests passed OK --------------- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Wed Apr 29 20:54:23 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011587.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Wed Apr 29 20:56:28 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011588.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Wed Apr 29 20:58:34 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011589.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Wed Apr 29 21:00:35 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011590.html Subject: OK : Zope-trunk Python-2.6.1 : Linux From: Zope Tests Date: Wed Apr 29 21:02:36 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011591.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Wed Apr 29 21:04:36 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011592.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Wed Apr 29 21:06:37 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011593.html Subject: OK : Zope-trunk-alltests Python-2.6.1 : Linux From: Zope Tests Date: Wed Apr 29 21:08:37 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011594.html

1 0

Zope Tests: 8 OK
by Zope Tests Summarizer 29 Apr '09

29 Apr '09

Summary of messages to the zope-tests list. Period Tue Apr 28 12:00:00 2009 UTC to Wed Apr 29 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Tests passed OK --------------- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Tue Apr 28 20:51:05 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011579.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Tue Apr 28 20:53:07 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011580.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Tue Apr 28 20:55:07 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011581.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Tue Apr 28 20:57:08 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011582.html Subject: OK : Zope-trunk Python-2.6.1 : Linux From: Zope Tests Date: Tue Apr 28 20:59:14 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011583.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Tue Apr 28 21:01:15 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011584.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Tue Apr 28 21:03:16 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011585.html Subject: OK : Zope-trunk-alltests Python-2.6.1 : Linux From: Zope Tests Date: Tue Apr 28 21:05:16 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011586.html

1 0

Re: [Zope-dev] SVN: zope.traversing/trunk/ zcml now only depends on zope.component meta, not zope.app.component
by Tres Seaver 29 Apr '09

29 Apr '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Gary Poster wrote: > Log message for revision 98787: > zcml now only depends on zope.component meta, not zope.app.component > > Changed: > U zope.traversing/trunk/CHANGES.txt > U zope.traversing/trunk/src/zope/traversing/configure.zcml > A zope.traversing/trunk/src/zope/traversing/tests/ftest_zcml_dependencies.zcml > A zope.traversing/trunk/src/zope/traversing/tests/test_dependencies.py > > -=- > Modified: zope.traversing/trunk/CHANGES.txt > =================================================================== > --- zope.traversing/trunk/CHANGES.txt 2009-04-02 02:22:07 UTC (rev 98786) > +++ zope.traversing/trunk/CHANGES.txt 2009-04-02 06:46:52 UTC (rev 98787) > @@ -5,7 +5,7 @@ > 3.5.4 (unreleased) > ------------------ > > -- ... > +- Change configure.zcml to not depend on zope.app.component. > > 3.5.3 (2009-03-10) > ------------------ > > Modified: zope.traversing/trunk/src/zope/traversing/configure.zcml > =================================================================== > --- zope.traversing/trunk/src/zope/traversing/configure.zcml 2009-04-02 02:22:07 UTC (rev 98786) > +++ zope.traversing/trunk/src/zope/traversing/configure.zcml 2009-04-02 06:46:52 UTC (rev 98787) > @@ -16,10 +16,10 @@ > provides="zope.traversing.interfaces.ITraversable" for="*" > factory="zope.traversing.namespace.etc" > /> > -<view > +<adapter > name="etc" > - type="zope.interface.Interface" > - provides="zope.traversing.interfaces.ITraversable" for="*" > + for="* zope.publisher.interfaces.IRequest" > + provides="zope.traversing.interfaces.ITraversable" > factory="zope.traversing.namespace.etc" > /> > ... Excellent fix. 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 iD8DBQFJ1PEi+gerLs4ltQ4RAo7yAKCG3khpLFSM3pB/4GhtgaCVow/63wCgsHKF QooMuQx3Htwl6K0hBFr12vU= =o9k5 -----END PGP SIGNATURE-----

3 4

Defining Zope 3.
by Lennart Regebro 28 Apr '09

28 Apr '09

Here are a list of things I have seen that you may mean when you say "Zope 3". I'm sure I missed several: 1. Whatever is included in the Zope 3 tgz that you download. 2. All the packages included in the Zope 3 KGS. (Should be the same as 1, if I understand correctly.) 3. 1 or 2 minus the ZMI. 4. The zope.app.publication publisher. 5. A loose set of packages starting with zope.*, zc.* and z3c.* 6. A strictly defined (by the Zope Toolkit KGS) set of packages starting with zope.*, zc.* and z3c.* that is central and common to Zope 3 in the sense of 1 or 2, and also Grok and Zope 2. 7. Technologies that you use when you develop with the packages in 5 and 6. I propose that the name Zope 3 applies *only* to 1 and 2. If future versions of 1 or 2 gets released without the ZMI (as discussed in other threads), then of course 1, 2 and 3 is the same. Opinions? -- Lennart Regebro: Python, Zope, Plone, Grok http://regebro.wordpress.com/ +33 661 58 14 64

20 69

Publishing buildout [versions] blocks for releases
by Martin Aspeli 28 Apr '09

28 Apr '09

Hi folks, I've written a small Google App Engine application to help manage and publish buildout configuration that provide a known good [versions] block. I'm not sure this approach is good, and the application is not well tested, but it may be of interest to some people here. http://good-py.appspot.com http://www.martinaspeli.net/articles/hello-good-py-a-known-good-versions-ma… The code's in the collective, so I welcome improvements. I think it is at lest interesting using GAE for this type of thing, whether this particular application is the approach or not. Cheers, Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book

1 0

Re: [Zope-dev] CMF Tests: 2 OK, 5 Unknown
by Andreas Jung 28 Apr '09

28 Apr '09

On 28.04.2009 15:25 Uhr, Tres Seaver wrote: > ml > > These tests are breaking because a much newer version of zope.component > (3.7.0) is being installed than the on called out in the Zope 2 index[1] > (3.5.1). That version is older than the one in the Zope 2 > versions.cfg[1] (3.6.0). > > [1] http://download.zope.org/Zope2/index/2.12.0a4/zope.component/ > > [2] http://svn.zope.org/Zope/trunk/versions.cfg?rev=99525&view=auto Hanno updated versions.cfg two days ago. Andreas

2 4

[Feature Request] add 'extensions' option to z3c.recipe.sphinxdoc
by markus korn 28 Apr '09

28 Apr '09

Hi, I'm using z3c.recipe.sphinxdoc to generate documentation for a project. Sphinx has some very useful extensions like 'sphinx.ext.autodoc' and 'sphinx.ext.doctest' and I would like to use both extensions in my 'docs' part. Especially the autodoc function is useful when creating API docs. I would be cool if 'z3c.recipe.sphinxdoc' could take an additional option to include extensions, like: [docs] recipe = z3c.recipe.sphinxdoc eggs = someeeg extensions = sphinx.ext.autodoc sphinx.ext.doctest Thanks, Markus

2 2

Zope Tests: 8 OK
by Zope Tests Summarizer 28 Apr '09

28 Apr '09

Summary of messages to the zope-tests list. Period Mon Apr 27 12:00:00 2009 UTC to Tue Apr 28 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Tests passed OK --------------- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Mon Apr 27 20:50:44 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011571.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Mon Apr 27 20:52:54 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011572.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Mon Apr 27 20:54:59 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011573.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Mon Apr 27 20:57:00 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011574.html Subject: OK : Zope-trunk Python-2.6.1 : Linux From: Zope Tests Date: Mon Apr 27 20:59:01 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011575.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Mon Apr 27 21:01:01 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011576.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Mon Apr 27 21:03:01 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011577.html Subject: OK : Zope-trunk-alltests Python-2.6.1 : Linux From: Zope Tests Date: Mon Apr 27 21:05:04 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011578.html

1 0

Release management proposal
by Wichert Akkerman 28 Apr '09

28 Apr '09

I want to suggest two changes to the standard release process: 1. use "sdist --formats=zip". This works around a nasty bug in the python 2.4 tarfile module which makes it skip files with a path of a specific length. This can make a release impossible to use. 2. forbid the use of __file__ in setup.py. This breaks on systems which do not have setuptools installed globally but rely on a (zc.buildout-created) wrapper script. __file__ will point to the wrapper script in those instances, which breaks setup.py. Wichert. -- Wichert Akkerman <wichert(a)wiggy.net> It is simple to make things. http://www.wiggy.net/ It is hard to make things simple.

8 20

Re: [Zope-dev] [Checkins] SVN: zope.publisher/trunk/ Added some BBB code to setDefaultSkin
by Hanno Schlichting 28 Apr '09

28 Apr '09

Hi. Roger Ineichen wrote: >> Log message for revision 99518: >> Added some BBB code to setDefaultSkin to allow >> IBrowserRequest's to continue to work without configuring any >> special adapter for IDefaultSkin. Lot's of code inside Zope2 >> relying on using the request object without tons of CA setup > > I don't comment this. > > but, > You broke my hole refactoring. My refactoring was making it > possible to use IDefaultBrowserLayer less IBrowserRequest. > > Your changes apply now to every IBrowserRequest an > IDefaultBrowserLayer where explicit was no default > layer configured for. This is bad because and makes > the previous refactoring obsolate. > > Can you revert this changes? Then there's some tests and description missing proving that intent. All I could read in the changelog and the skinnable tests was pointing in the other direction: Making it possible to use the Skinnable concept without relying on IBrowserRequest. The whole JSONRequest (which is not a BrowserRequest) tests inside skinnable.txt continue to work. All I did here was to move two constructs from ZCML into direct code. The lines I added do exactly the same as the default adapter registered as: <adapter name="default" factory=".skinnable.getDefaultSkin" for="zope.publisher.interfaces.browser.IBrowserRequest" provides="zope.publisher.interfaces.IDefaultSkin" /> Unless I got something wrong, no behavior was changed if you load zope.publisher's configure.zcml. For Zope2 it is now just possible to continue to ignore that configure.zcml as it had done before. Hanno

2 4