February 2009 - Zope-Dev

Zope 3.4.0 Released!
by Stephan Richter 03 Feb '09

03 Feb '09

Hi everyone, It is finally here! Thanks goes to everyone who involved! January 29, 2009 - The Zope 3 development team announces the Zope 3.4.0 release. After 2 years of development, the Zope Foundation and the larger Zope community is proud to announce the release of Zope 3.4.0. The focus of the Zope 3.4 development effort has been the conversion from a monolithic source tree, to a set of many small packages (eggs), that can be used independently of each other. The core has been further stabilized through numerous bug fixes, and many new add-on packages have been developed to provide a richer development experience. With this release also comes a renewed commitment to a short and reliable release cycle of 6 months. Packages and Eggs ----------------- Zope 3 is now fully converted to an egg-based system. While some work still remains, it integrates very well with the rest of the Python community. The conversion to egg-based packaging also enables other Python developers to only have to use small bits and pieces of the complete Zope software system. The conversion means that Zope 3 developers do not use the classic Zope 3 tar-ball release anymore. However, for your convenience, Zope 3 developers will provide the classic Zope 3 tar ball releases for at least the 3.4 series and probably for 3.5 as well. So how are Zope 3 applications built using only eggs? The Known Good Set (KGS) ~~~~~~~~~~~~~~~~~~~~~~~~ The known good set -- or in short KGS -- is a configuration of packages and their versions that are known to work well together. The compatibility is frequently verified by running over twelve thousand tests on a daily basis [1]_. The KGS is tested against Python 2.4 and 2.5 on the 32- and 64-bit platforms. The list of controlled packages and their versions for Zope 3.4 can be found at the Zope 3 KGS site [2]_. The KGS can be used in several ways [3]_. The most common way is to "nail" the versions by downloading the version configuration file [4]_ and insert them as follows in your buildout configuration:: [buildout] versions = versions ... [versions] zope.interface = 3.4.0 ... ``zopeproject`` Project Builder ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ To start building a project using a common setup, a package called `zopeproject` can be used to quickly setup the boilerplate for the project. Ample documentation is provided at the `zopeproject` home page [5]_. `zopeproject` uses Paste or ZDaemon to create a working server. The following commands get you started:: $ easy_install zopeproject $ zopeproject HelloWorld $ cd HelloWorld $ bin/helloworld-ctl foreground Demo Packages ~~~~~~~~~~~~~ At this point, there is no demo package demonstrating a simple Zope 3 application setup. However, the ``z3c.formdemo`` package can be used as a fairly minimal setup. To get started with it, enter the following:: $ svn co svn://svn.zope.org/repos/main/z3c.formdemo/tags/1.5.3 formdemo $ cd formdemo $ python bootstrap.py $ ./bin/buildout -v $ ./bin/demo fg .. [1] http://zope3.pov.lt/buildbot .. [2] http://download.zope.org/zope3.4/3.4.0/controlled-packages.cfg .. [3] http://download.zope.org/zope3.4/intro.html .. [4] http://download.zope.org/zope3.4/3.4.0/versions.cfg .. [5] http://pypi.python.org/pypi/zopeproject Downloads --------- - Zope 3.4 KGS: http://download.zope.org/zope3.4 - Zope 3.4 Controlled Packages: http://download.zope.org/zope3.4/3.4.0/controlled-packages.cfg - Zope 3.4 Versions: http://download.zope.org/zope3.4/3.4.0/versions.cfg - The classic Zope 3 source release can be downloaded from: http://download.zope.org/zope3.4/3.4.0/Zope-3.4.0.tgz Installation instructions for both Windows and Un*x/Linux are now available in the top level `README.txt` file of the distribution. The binary installer is recommended for Windows. Zope 3.4 requires Python 2.4 or 3.5 to run. You must also have zlib installed on your system. Resources --------- - Zope 3 Development Web Site: http://wiki.zope.org/zope3 - Zope 3 Developers Mailing List: http://mail.zope.org/mailman/listinfo/zope-dev Retired: http://mail.zope.org/mailman/listinfo/zope3-dev - Zope 3 Users Mailing List: http://mail.zope.org/mailman/listinfo/zope-users - Bug tracker at launchpad: https://launchpad.net/zope3 - IRC Channel: #zope3-dev at irc.freenode.net About Zope 3 ------------ Zope 3 is a web application server that continues to build on the heritage of Zope. It was rewritten from scratch based on the latest software design patterns and the experiences of Zope 2. The component architecture is the very core of Zope 3 that allows developers to create flexible and powerful web applications. Compatibility with Zope 2 ~~~~~~~~~~~~~~~~~~~~~~~~~ Zope 3 is not upwards compatible with Zope 2. This means you cannot run Zope 2 applications in Zope 3. We continue to work on the transition from Zope 2 to Zope 3 by making Zope 2 use more and more of the Zope 3 infrastructure. This means that new code written in Zope 2 can benefit from Zope 3 technology. Also, with care, code can be written that works in both Zope 3 and Zope 2. This allows a Zope 2 application to slowly evolve towards Zope 3. Unchanged Zope 2 applications are never expected to work in Zope 3, however. About the Zope Foundation ------------------------- The Zope Foundation, based in Fredricksburg, Virginia, is a not-for-profit organisation that provides support for the Zope community and the Zope platform and its associated software. Its community includes the open source community of contributers as well as the community of businesses and organizations that use Zope.

10 23

How can we update our source?
by Roger Ineichen 03 Feb '09

03 Feb '09

Hi all First, thanks to the great refactoring work! Can someone give a summary about what got moved or is there another way to find out what I need to change in z3c and own packages? I guess there must be an update strategy since we skipped the deprecation message which I don't know. or not? Regards Roger Ineichen _____________________________ END OF MESSAGE

4 4

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