- Zope-Dev - Zope lists

Zope 3.5dev KGS
by Stephan Richter 03 Feb '09

03 Feb '09

Hi everyone, I have setup a KGS for Zope 3.5, so that people can test the development KGS. http://download.zope.org/zope3.5/ I have updated all packages to the latest version available. I have not tested anything. I would like someone to setup a buildbot like at http://zope3.pov.lt/buildbot/ Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. "Zope Stephan Richter"

6 10

Zope Tests: 8 OK
by Zope Tests Summarizer 02 Feb '09

02 Feb '09

Summary of messages to the zope-tests list. Period Sun Feb 1 12:00:00 2009 UTC to Mon Feb 2 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.7 : Linux From: Zope Tests Date: Sun Feb 1 20:42:38 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/010991.html Subject: OK : Zope-2.9 Python-2.4.5 : Linux From: Zope Tests Date: Sun Feb 1 20:44:12 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/010992.html Subject: OK : Zope-2.10 Python-2.4.5 : Linux From: Zope Tests Date: Sun Feb 1 20:45:42 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/010993.html Subject: OK : Zope-2.11 Python-2.4.5 : Linux From: Zope Tests Date: Sun Feb 1 20:47:12 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/010994.html Subject: OK : Zope-trunk Python-2.4.5 : Linux From: Zope Tests Date: Sun Feb 1 20:48:42 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/010995.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Sun Feb 1 20:50:13 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/010996.html Subject: OK : Zope[2.buildout]-trunk Python-2.4.5 : Linux From: Zope Tests Date: Sun Feb 1 20:51:47 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/010997.html Subject: OK : Zope[2.buildout]-trunk Python-2.5.4 : Linux From: Zope Tests Date: Sun Feb 1 20:53:28 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/010998.html

1 0

Post-Sprint releases done -- a few tests failing
by Christian Theune 01 Feb '09

01 Feb '09

Hi, I just released the last packages after the sprint. While running the compatibility tests of all currently released packages I found the following packages to fail: compat-zope.testing already failed before, the tests seem incompatible with Python 2.4 compat-zope.introspector seems to rely on zapi to be available but not declared as a dependency compat-zope.globalrequest seems to rely on zope.app.testing without declaring the dependency compat-zope.app.keyreference doctest comparison error, probably this is still in flux as Dan is working on that compat-zope.psycopgda compat-zope.sqlalchemy those two fail because of my machine not having compatible libraries around I think in overall we're doing pretty (6 out of 143) well compared to before the sprint (we found quite a few more packages in a broken state) as none of those seem to be "real" problems. 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 7 · fax +49 345 1229889 1 Zope and Plone consulting and development

2 2

Fw: ** PROBLEM alert - Zope Project Services (SVN/Downloads/Mailman/...)/KGS age is WARNING **
by Christian Theune 01 Feb '09

01 Feb '09

Hi, the KGS turned from not-having-been-updated to missing. At least regarding to my monitoring. What's happened? Begin forwarded message: Date: Sat, 31 Jan 2009 07:09:44 +0100 (CET) From: nagios(a)mail.whq.gocept.com (nagios) To: ct(a)gocept.com Subject: ** PROBLEM alert - Zope Project Services (SVN/Downloads/Mailman/...)/KGS age is WARNING ** ***** Nagios ***** Notification Type: PROBLEM Service: KGS age Host: Zope Project Services (SVN/Downloads/Mailman/...) Address: download.zope.org State: WARNING Date/Time: Sat Jan 31 07:09:44 CET 2009 Additional Info: HTTP WARNING: HTTP/1.1 404 Not Found -- 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

5 15

Re: [Zope-dev] [Checkins] SVN: zope.app.apidoc/trunk/s - savepoint.txt moved out of the tests directory, follow.
by Dan Korostelev 01 Feb '09

01 Feb '09

2009/1/30 Christian Theune <ct(a)gocept.com>: > Log message for revision 95598: > - savepoint.txt moved out of the tests directory, follow. > - Fix UI changes in tests depending on the new zope.site module. savepoint.txt is out of tests directory only on ZODB 3.8, but it is in tests of transaction 1.0a1 that's is a dependency of ZODB 3.9. So I changed the path to tests/savepoint.txt in that ZCML some time before. You unfixed the https://bugs.launchpad.net/zope3/+bug/303721 :) -- WBR, Dan Korostelev

2 1

Zope Tests: 8 OK
by Zope Tests Summarizer 01 Feb '09

01 Feb '09

Summary of messages to the zope-tests list. Period Sat Jan 31 12:00:00 2009 UTC to Sun Feb 1 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.7 : Linux From: Zope Tests Date: Sat Jan 31 20:44:17 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-January/010983.html Subject: OK : Zope-2.9 Python-2.4.5 : Linux From: Zope Tests Date: Sat Jan 31 20:45:48 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-January/010984.html Subject: OK : Zope-2.10 Python-2.4.5 : Linux From: Zope Tests Date: Sat Jan 31 20:47:18 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-January/010985.html Subject: OK : Zope-2.11 Python-2.4.5 : Linux From: Zope Tests Date: Sat Jan 31 20:48:49 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-January/010986.html Subject: OK : Zope-trunk Python-2.4.5 : Linux From: Zope Tests Date: Sat Jan 31 20:50:19 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-January/010987.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Sat Jan 31 20:51:50 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-January/010988.html Subject: OK : Zope[2.buildout]-trunk Python-2.4.5 : Linux From: Zope Tests Date: Sat Jan 31 20:53:21 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-January/010989.html Subject: OK : Zope[2.buildout]-trunk Python-2.5.4 : Linux From: Zope Tests Date: Sat Jan 31 20:54:54 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-January/010990.html

1 0

Progress on zope intid/keyreference.
by Dan Korostelev 01 Feb '09

01 Feb '09

I just finished working on zope's intid and keyreference packages. The whole key-reference stuff is now moved in zope.keyreference package and the new version of zope.app.keyreference is released that only contains compatibility imports, so it makes no sense to depend on zope.app.keyreference anymore - use zope.keyreference. All functionality of zope.app.intid, except ZMI stuff is moved to the zope.intid package. Old zope.app.intid package now only contains browser pages and add menu item as well as backward-compatiblity imports. So if you are not using ZMI - zope.intid is for you. Next, I'm going to split zope.app.catalog and check other packages for uses of zope.app.intid/zope.app.keyreference (I guess some sqlalchemy-related packages can depend on keyreference stuff). -- WBR, Dan Korostelev

2 3

Grok cave sprint summary, and future todos
by Martijn Faassen 01 Feb '09

01 Feb '09

Hi there, I've just made a lot of releases as the result of our dependency cleanup sprint. There are more releases to be made, but I think I've released the most important affected packages now. Christian Theune is going to follow up and release some more packages that we touched, probably tomorrow. I'm going to write up a document that describes how we analyzed dependencies and what approaches we took so that people who want to help have some idea of what to do. the most important affected packages are (as far as I can remember): zope.app.component ('class' ZCML directive moved into zope.security, site stuff extracted into zope.site) zope.app.security ('module' directive moved into zope.security, along with some helper functions) zope.app.container (most functionality moved into zope.container) zope.app.folder (base class moved into zope.container, Folder itself moved into zope.site as its main function was to mix in site management facilities) zope.traversing (depends on zope.location now instead of the other way around) zope.location (doesn't depend on zope.traversing anymore) zope.site (a new package extracted from zope.app.component and zope.app.folder) zope.container (a new package extracted from zope.app.container and zope.app.folder) Another thing we want to do is reduce the test dependencies of packages to almost nothing (or nothing at all). We think it'd be good if package only used what they depend on directly for testing purposes; testing dependencies in general should follow implementation dependencies. This might allow us to get rid of zope.app.testing at some point. Instead we'd like to see more (and more consistent!) 'testing' modules in packages that help with test setup. We have created a bunch of tools in the process of reducing dependencies: an extension to the test runner to track imports that could be modified to be from a better location (though 'grep' is very useful there too), z3c.recipe.compattest, and Christian Theune is working on a way to 'touch' the ZODB so that it will update any moved class to the new location. Note that we haven't finished going through the codebase changing imports from zope.app.folder to zope.site where possible - volunteers are welcome. This should further reduce dependencies in the entire graph as zope.site pulls in far less than zope.app.folder. If a bunch of us keep this up we'll that'll allow us to start retiring a lot of packages that are mostly unused, and have a smaller, easier set of Zope 3 packages to maintain and understand. Users of the Zope 3 libraries (plain Zope 3, Grok, Zope 2, Repoze, and others) should all benefit from this. Regards, Martijn

2 6

zope.app.keyreference, zope.app.intid and zope.app.catalog
by Dan Korostelev 31 Jan '09

31 Jan '09

While you guys are moving zope.app.container to zope.container and those cleaning many dependencies, I'd also like to clean intid/catalog related stuff. The whole thing consists of three main packages that can be cleaned: * zope.app.keyreference - it doesn't depend on any ZMI or container stuff, it's just a simple package defining the IKeyReference interface and implementing it for persistent objects. I'd like to rename the package to just zope.keyreference (and making z.a.keyreference depend on it). * zope.app.intid - this one depends on container stuff, because of events and also defines some ZMI views. The events are not a problem anymore, because we have zope.container now, but the ZMI stuff requires zope.app.publisher (though it's not in direct requirements for some reason). I'd like to move all stuff except browser pages to the zope.intid package. * zope.app.catalog - pretty the same story as zope.app.intid, but it also uses zope.app.form's auto-form-directives. I'd like to move the non-ZMI code to plain zope.catalog. However, it's still not clear to me what should we do with old imports and pickled objects (there are "over 9000" of them in case of key-references). I'd like to make non-deprecated backward-compatibilty imports in the old places until we have a generic and easy-to-use tool for "touching" ZODB objects. Suggestions/objections? -- WBR, Dan Korostelev

3 7

OSCON 2009 Call For Participation ends Feb 3rd - No Zope proposals yet
by Michael R. Bernstein 31 Jan '09

31 Jan '09

Hi folks, The deadline for the O'Reilly Open Source Convention Call For Participation is Tuesday Feb 3rd. OSCON will be held July 20-24 in San Jose, California. As of today, there are no Zope-related proposals, so yours could have a pretty good chance of acceptance. ;-) There have been a lot of exciting developments in the Zope world in the past year, and I for one would really like Zope to get more public exposure. So please, write up your proposals and submit them before the deadline! For more information, see http://conferences.oreilly.com/oscon http://en.oreilly.com/oscon2009/public/cfp/57 Cheers, - Michael Bernstein

1 0