- Zope-Dev - Zope lists

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

09 Feb '09

Summary of messages to the zope-tests list. Period Sun Feb 8 12:00:00 2009 UTC to Mon Feb 9 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Test failures ------------- Subject: FAILED (failures=1) : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Sun Feb 8 21:01:53 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011064.html Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.7 : Linux From: Zope Tests Date: Sun Feb 8 20:47:39 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011057.html Subject: OK : Zope-2.9 Python-2.4.5 : Linux From: Zope Tests Date: Sun Feb 8 20:49:42 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011058.html Subject: OK : Zope-2.10 Python-2.4.5 : Linux From: Zope Tests Date: Sun Feb 8 20:51:42 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011059.html Subject: OK : Zope-2.11 Python-2.4.5 : Linux From: Zope Tests Date: Sun Feb 8 20:53:43 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011060.html Subject: OK : Zope-trunk Python-2.4.5 : Linux From: Zope Tests Date: Sun Feb 8 20:55:47 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011061.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Sun Feb 8 20:57:48 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011062.html Subject: OK : Zope-trunk-alltests Python-2.4.5 : Linux From: Zope Tests Date: Sun Feb 8 20:59:49 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011063.html

1 0

Re: [Zope-dev] [Checkins] SVN: z3c.layer/tags/0.3.0/setup.py -dev
by Michael Howitz 09 Feb '09

09 Feb '09

Am 08.02.2009 um 05:14 schrieb Stephan Richter: > On Saturday 07 February 2009, Michael Howitz wrote: >> Changed: >> U z3c.layer/tags/0.3.0/setup.py > > I'll note that we retired this package in favor of > > z3c.layer.minimal > z3c.layer.trusted > etc. Thanks for clarification. After releasing z3c.layer I noticed the other packages. So I'll do another release pointing to the split-of packages and delete the trunk of z3c.layer so it is clear that the package is dead. 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

1 0

zope.location.pickling.PathPersistent
by Dan Korostelev 08 Feb '09

08 Feb '09

Hi there. While refactoring zope.location to use the new zope.copy package, I came on PathPersistent class in the zope.location.pickling module. It does quite the same as old CopyPersistent, but based on object location paths instead of ids. I can't find any code that actually uses that class and I don't think that it makes much sense. So I'd propose to just remove it. What do you people think? Also, Martijn, Christian, was it the only reason for moving ITraverser interface from zope.traversing to zope.location? If so, can we still move it back? -- WBR, Dan Korostelev

1 0

Merge zc.copy with zope.copypastemove and zope.location.
by Dan Korostelev 08 Feb '09

08 Feb '09

The README.txt of zc.copy says that the components, provided by this package is apropriate for inclusion in Zope itself. The package provides a more pluggable mechanism for copying generic persistent objects (not only ILocation's) as well as a way to register post-copy hooks to be executed, which is very useful, for example when dealing with persistent objects that have non-ZODB bits (like filesystem based files related and so on). However, the package is really small and mostly contains modified copies of zope.copypastemove's ObjectCopier and zope.location's locationCopy. So, I propose to merge the zc.copy package's changes with original zope.copypastemove/zope.location and deprecate it. If noone objects, I'll do that myself. -- WBR, Dan Korostelev

2 5

Zope Tests: 6 OK, 4 Failed
by Zope Tests Summarizer 08 Feb '09

08 Feb '09

Summary of messages to the zope-tests list. Period Sat Feb 7 12:00:00 2009 UTC to Sun Feb 8 12:00:00 2009 UTC. There were 10 messages: 10 from Zope Tests. Test failures ------------- Subject: FAILED (failures=6) : Zope-trunk Python-2.4.5 : Linux From: Zope Tests Date: Sat Feb 7 21:10:33 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011051.html Subject: FAILED (failures=7) : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Sat Feb 7 21:12:03 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011052.html Subject: FAILED (failures=6) : Zope[2.buildout]-trunk-alltests Python-2.4.5 : Linux From: Zope Tests Date: Sat Feb 7 21:16:35 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011055.html Subject: FAILED (failures=7) : Zope[2.buildout]-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Sat Feb 7 21:18:05 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011056.html Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.7 : Linux From: Zope Tests Date: Sat Feb 7 21:04:32 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011047.html Subject: OK : Zope-2.9 Python-2.4.5 : Linux From: Zope Tests Date: Sat Feb 7 21:06:02 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011048.html Subject: OK : Zope-2.10 Python-2.4.5 : Linux From: Zope Tests Date: Sat Feb 7 21:07:32 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011049.html Subject: OK : Zope-2.11 Python-2.4.5 : Linux From: Zope Tests Date: Sat Feb 7 21:09:02 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011050.html Subject: OK : Zope[2.buildout]-trunk Python-2.4.5 : Linux From: Zope Tests Date: Sat Feb 7 21:13:33 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011053.html Subject: OK : Zope[2.buildout]-trunk Python-2.5.4 : Linux From: Zope Tests Date: Sat Feb 7 21:15:03 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011054.html

1 0

Zope Tests: 6 OK, 4 Failed
by Zope Tests Summarizer 07 Feb '09

07 Feb '09

Summary of messages to the zope-tests list. Period Fri Feb 6 12:00:00 2009 UTC to Sat Feb 7 12:00:00 2009 UTC. There were 10 messages: 10 from Zope Tests. Test failures ------------- Subject: FAILED (failures=6) : Zope-trunk Python-2.4.5 : Linux From: Zope Tests Date: Fri Feb 6 21:19:46 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011041.html Subject: FAILED (failures=7) : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Fri Feb 6 21:21:19 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011042.html Subject: FAILED (failures=6) : Zope[2.buildout]-trunk-alltests Python-2.4.5 : Linux From: Zope Tests Date: Fri Feb 6 21:26:03 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011045.html Subject: FAILED (failures=7) : Zope[2.buildout]-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Fri Feb 6 21:27:33 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011046.html Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.7 : Linux From: Zope Tests Date: Fri Feb 6 21:13:43 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011037.html Subject: OK : Zope-2.9 Python-2.4.5 : Linux From: Zope Tests Date: Fri Feb 6 21:15:14 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011038.html Subject: OK : Zope-2.10 Python-2.4.5 : Linux From: Zope Tests Date: Fri Feb 6 21:16:46 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011039.html Subject: OK : Zope-2.11 Python-2.4.5 : Linux From: Zope Tests Date: Fri Feb 6 21:18:16 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011040.html Subject: OK : Zope[2.buildout]-trunk Python-2.4.5 : Linux From: Zope Tests Date: Fri Feb 6 21:22:49 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011043.html Subject: OK : Zope[2.buildout]-trunk Python-2.5.4 : Linux From: Zope Tests Date: Fri Feb 6 21:24:33 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011044.html

1 0

Re: [Zope-dev] SVN: zope.app.component/trunk/ Please, don't just remove things that could be used in users code.
by Martijn Faassen 06 Feb '09

06 Feb '09

Dan Korostelev wrote: > Log message for revision 96156: > Please, don't just remove things that could be used in users code. > > Changed: > U zope.app.component/trunk/CHANGES.txt > U zope.app.component/trunk/src/zope/app/component/metadirectives.py > > -=- > Modified: zope.app.component/trunk/CHANGES.txt > =================================================================== > --- zope.app.component/trunk/CHANGES.txt 2009-02-05 18:07:51 UTC (rev 96155) > +++ zope.app.component/trunk/CHANGES.txt 2009-02-05 18:22:19 UTC (rev 96156) > @@ -5,7 +5,9 @@ > 3.6.1 (unreleased) > ------------------ > > -- ... > +- Make ``class`` directive schemas importable from old location, > + raising a deprecation warning. It was moved in the previous release, > + but some custom directives could possibly use its schemas. Out of curiosity, *was* it used by custom directives that you know of? A more philosophical question: are the interfaces used to implement a directive part of a public API that is reusable or not? When we moved the directive implementation I arbitrary made the assumption that it'd be fine to just move them wholesale, but you clearly don't agree. Besides the interfaces, should the implementation also have backwards compatibility imports? I guess sometimes reuse by interface subclassing does happen in directive implementation, but of course we could declare that such reuse is only intra-package. In my mind, it's also less risky to move a directive implementation even if it is reused, as the amount of external reuse is likely rare and is less likely to be in end-user code. The developers of the code layered on top of the directive definition would therefore be quite capable of fixing any breakage quickly. But of course placing a few imports for backwards compatibility is not a lot of work and may be the easiest way out of this set of questions. :) Regards, Martijn

4 7

Important release migration information
by Dan Korostelev 06 Feb '09

06 Feb '09

I just committed a new section to zope3docs about migration to newer Zope 3 releases. I think we should maintain a list of most important changes that could break backward-compatibility, like recent changing exception types used in zope.container in a separate document, so people who are upgrading from, say, Zope 3.4 to Zope 3.5 could easily find the bits about problems that can pop up in the transition. What are you thinking about that? -- WBR, Dan Korostelev

2 3

Can somebody upload a zope.app.zcmlfiles 3.5.3 release?
by Tres Seaver 06 Feb '09

06 Feb '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ... or grant me the PyPI role needed? http://svn.zope.org/zope.app.zcmlfiles/tags/3.5.3 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 iD8DBQFJijb/+gerLs4ltQ4RAnEHAKDJnCwofSVkkPnWbkuGgCtYk3tOzwCfQ0c1 cDnFqEDDoA/tqzTcJHc4LqU= =oFZo -----END PGP SIGNATURE-----

6 11

Plans for Zope 2.12
by Andreas Jung 06 Feb '09

06 Feb '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi there, based on an earlier Zope 2.12 thread http://mail.zope.org/pipermail/zope-dev/2008-October/033572.html I propose that we get out an alpha version of Zope 2.12 by end of February. http://mail.zope.org/pipermail/zope-dev/2008-October/033572.html Major changes: - - dropping Python 2.4 support officially (Python 2.4 is no longer officially supported by the Python developers so we can not safely support it) - - focus on Python 2.6 support for the final release (although there are still some tests failing - more than with Python 2.5). Possibly focus on Python 2.5 support for the alpha phase. Not sure if we want to support Python 2.5 and 2.6 officially at the same time. With the current classification of Python versions within the configure script I would suggest: TARGET=Python 2.6.X ACCEPTABLE=Python 2.5 Python 2.4.X would be basically not acceptable but could be used at your own risk using the --with-python option. - - complete eggification (apparently pretty much done) - - reducing Zope 3 dependencies (apparently pretty much done) - - removing ZClasses completely - - ship with ZODB 3.9 (currently in alpha stage) Rough edges/open points I encountered so far: - - RestrictedPython security audit: such an audit has been made by Stefan and Sidnei. I am not qualified to speak about the correctness of the audit. I assume they know what they were doing. Unless objections one might consider this issue as resolved - if not, please speak up. - - creation of some skripts e.g. "mkzeoinstance" when easy_install-ing the Zope 2 source distro does not seem to work or it is still missing - - how do to a "traditional" SVN checkout of the Zope 2 and the related Zope 3 modules? The Zope2.buildout maintains its dependencies through a KGS - the old-style SVN checkout uses svn:external. I think there is a need for having both and don't know of a save way for keeping the svn:externals and the KGS in sync (without additional manual effort). Andreas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkl3KWoACgkQCJIWIbr9KYyKOwCfVI+gU1AZsIstWies9BVRGr4l +LcAn1MBC0jsed690vpeU2TJzYUz6xQ+ =YZQ/ -----END PGP SIGNATURE-----

12 27