December 2005 - Zope-Dev

Zope tests: 7 OK, 1 Failed
by Zope tests summarizer 23 Dec '05

23 Dec '05

Summary of messages to the zope-tests list. Period Thu Dec 22 12:01:01 2005 UTC to Fri Dec 23 12:01:01 2005 UTC. There were 8 messages: 8 from Zope Unit Tests. Test failures ------------- Subject: FAILED : Zope-trunk Python-2.4.2 : Linux From: Zope Unit Tests Date: Thu Dec 22 21:13:41 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003833.html Tests passed OK --------------- Subject: OK : Zope-2_6-branch Python-2.1.3 : Linux From: Zope Unit Tests Date: Thu Dec 22 21:03:10 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003826.html Subject: OK : Zope-2_6-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Thu Dec 22 21:04:41 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003827.html Subject: OK : Zope-2_7-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Thu Dec 22 21:06:11 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003828.html Subject: OK : Zope-2_7-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Thu Dec 22 21:07:41 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003829.html Subject: OK : Zope-2_8-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Thu Dec 22 21:09:11 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003830.html Subject: OK : Zope-2_8-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Thu Dec 22 21:10:41 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003831.html Subject: OK : Zope-2_9-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Thu Dec 22 21:12:11 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003832.html

1 0

Zope 2.10: Wiki started
by Andreas Jung 23 Dec '05

23 Dec '05

I created a wiki for the 2.10 development: <http://www.zope.org/DevHome/Projects/Wikis/DevSite/Projects/Zope2.10/FrontP…> Feel free to contribute and comment. Andreas

2 1

zope-2.9 r40780 make install doesn't finish, files missing from bin
by Jeff Kowalczyk 23 Dec '05

23 Dec '05

I didn't receive any feedback on zope-general, but it could just be a problem with my environment that fails silently. Can anyone confirm that this isn't pilot error before I file a bug? Thanks. --- I'm having some trouble with the 'make install' stage of Zope-2.9 svn. Using python-2.4.2 on Gentoo linux. Zope-2.9.0b1 installed fine, but I needed the fix for get_transaction() ASAP. URL: svn://svn.zope.org/repos/main/Zope/branches/2.9 Revision: 40853 # ./configure --prefix=/usr/lib/zope-2.9.0 # make # make install (...) copying lib/python/zope/app/recorder/zope.app.recorder-configure.zcml -> /usr/lib/zope-2.9.0/zopeskel/etc/package-includes copying lib/python/zope/app/pluggableauth/zope.app.pluggableauth-configure.zcml -> /usr/lib/zope-2.9.0/zopeskel/etc/package-includes copying lib/python/zope/app/securitypolicy/securitypolicy-meta.zcml -> /usr/lib/zope-2.9.0/zopeskel/etc/package-includes copying lib/python/zope/testbrowser/testbrowser-ftesting.zcml -> /usr/lib/zope-2.9.0/zopeskel/etc/package-includes copying lib/python/zope/formlib/formlib-configure.zcml -> /usr/lib/zope-2.9.0/zopeskel/etc/package-includes copying lib/python/zope/app/securitypolicy/securitypolicy.zcml -> /usr/lib/zope-2.9.0/zopeskel/etc [ -f /usr/lib/zope-2.9.0/bin/python ] || ln -sfn "/usr/bin/python" /usr/lib/zope-2.9.0/bin/python Zope binaries installed successfully. Now run '/usr/lib/zope-2.9.0/bin/mkzopeinstance.py' This leaves (most visibly) many missing files in /usr/lib/zope-2.9.0/bin/. Only the 'python' symlink, and 'zconfig zconfig_schema2html zdctl.py zdrun.py' are installed there. Other files may be missing if they came afterwards, I don't have information on that. Is this line indicating a terminating error in make install? [ -f /usr/lib/zope-2.9.0/bin/python ] || ln -sfn "/usr/bin/python" /usr/lib/zope-2.9.0/bin/python Subsequent runs don't resume installing the remaining files: # make install "/usr/bin/python" "/home/jtk/software/svn/Zope/setup.py" \ build_ext -i \ install --home="/usr/lib/zope-2.9.0" running build_ext running build_headers running install running build running build_py running build_scripts running install_lib running install_headers running install_scripts changing mode of /usr/lib/zope-2.9.0/bin/zconfig to 755 changing mode of /usr/lib/zope-2.9.0/bin/zconfig_schema2html to 755 changing mode of /usr/lib/zope-2.9.0/bin/zdctl.py to 755 changing mode of /usr/lib/zope-2.9.0/bin/zdrun.py to 755 running install_data [ -f /usr/lib/zope-2.9.0/bin/python ] || ln -sfn "/usr/bin/python" /usr/lib/zope-2.9.0/bin/python Zope binaries installed successfully. Now run '/usr/lib/zope-2.9.0/bin/mkzopeinstance.py' Thanks for any insight on the issue. I don't think I want to run Zope in-place from the working copy.

12 35

What use cases are driving "make install" from a checkout?
by Jim Fulton 22 Dec '05

22 Dec '05

I'd like to step back and see if we can agree on what is driving the desire for "make install". I'll note that one reason is that it worked this way before, but I don't think that that is a good enough reason to delay the release. I'll note one use case: - A Zope deployer wants to deploy an unreleased version of Zope because they need some feature or bug fix that hasn't been released yet. Can anyone think of other use cases? Jim -- Jim Fulton mailto:jim@zope.com Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org

4 4

[RfC] Removal of old stuff in Zope 2.10
by Andreas Jung 22 Dec '05

22 Dec '05

Hi, for next release we plan to replace several parts with the corresponding components from Zope 3 (e.g. ZPT´). Philipp is working on a proposal on that issue. In addition I would like to get rid of some old stuff that is no longer maintained and buggy: - ZopeTutorial (could be ripped off without implications and made available for download on zope.org) - HelpSys - from a programmers view pretty much useless and not very helpful. I consider to replace it with something more useful (not sure we can re-use apidoc from Zope 3 in some way, perhaps the inclusion of Dieter's Docfinder might be more useful for programmers) - Gadfly(DA) - do we really need this? We discussed this already. In my opinion the purpose of Gadfly is only educational but nothing that one really needs or uses for production. It could be removed and made available for download on zope.org. And my favourite enemy in Zope: ZClasses :-) I would like to mark them _clearly_ as an obsolete feature (DeprecationWarning, Warnings in the ZMI and the Zope Book). I _don't_ propose to remove them at some point but ppl should be aware that they are using one of the most-scary components in Zope (please no further discussion about the pros and cons of ZClasses..this discussion took already place already a bunch of times on the list). -aj

19 51

Re: SVN: Zope/trunk/ deprecated ZGadfly/Gadfly
by Tres Seaver 22 Dec '05

22 Dec '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Andreas Jung wrote: > Log message for revision 40981: > deprecated ZGadfly/Gadfly > > > Changed: > U Zope/trunk/doc/CHANGES.txt > U Zope/trunk/lib/python/Products/ZGadflyDA/__init__.py > > -=- > Modified: Zope/trunk/doc/CHANGES.txt > =================================================================== > --- Zope/trunk/doc/CHANGES.txt 2005-12-22 11:32:11 UTC (rev 40980) > +++ Zope/trunk/doc/CHANGES.txt 2005-12-22 11:37:44 UTC (rev 40981) > @@ -28,6 +28,8 @@ > > - ZClasses are deprecated and should no longer be used. > > + - ZGadyFlyDA/Gadfly is deprecated > + > - Added a "clock server" servertype which allows users to > configure methods that should be called periodically as if > they were being called by a remote user agent on one of Zope's > > Modified: Zope/trunk/lib/python/Products/ZGadflyDA/__init__.py > =================================================================== > --- Zope/trunk/lib/python/Products/ZGadflyDA/__init__.py 2005-12-22 11:32:11 UTC (rev 40980) > +++ Zope/trunk/lib/python/Products/ZGadflyDA/__init__.py 2005-12-22 11:37:44 UTC (rev 40981) > @@ -15,6 +15,12 @@ > $Id$ > """ > > +import warnings > +warnings.warn('Using Gadfly and ZGadflyDA is deprecated. The module will be ' > + 'removed in Zope 2.11)', > + DeprecationWarning, > + stacklevel=2) > + > import Globals, os > > classes=('DA.Connection',) > Deprecation warnings at package scopy of a product aren't helpful, because they fire *every time Zope starts*, whether the person *uses* the deprecated pacakge or not. Let's find a way to trigger the warning from *third-party code*, but not from Zope code itself (I note that the ZClass warning spews every time, as well). Tres. - -- =================================================================== Tres Seaver +1 202-558-7113 tseaver(a)palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDqwT4+gerLs4ltQ4RAtrlAJ9qcT6Qhl5JR3lJRlwtxbxSA5iVGQCcCIXq edjqSCeMePJxdJFZVdPldTw= =hWk4 -----END PGP SIGNATURE-----

1 0

buildbot failure in Zope trunk 2.4 Linux zc-buildbot
by buildbot＠zope.com 22 Dec '05

22 Dec '05

The Buildbot has detected a failed build of Zope trunk 2.4 Linux zc-buildbot. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 2434 Blamelist: andreasjung BUILD FAILED: failed test sincerely, -The Buildbot

1 0

buildbot failure in Zope trunk 2.4 Linux zc-buildbot
by buildbot＠zope.com 22 Dec '05

22 Dec '05

The Buildbot has detected a failed build of Zope trunk 2.4 Linux zc-buildbot. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 2433 Blamelist: efge BUILD FAILED: failed test sincerely, -The Buildbot

1 0

Product installation (implicit vs. explicit)
by Chris McDonough 22 Dec '05

22 Dec '05

I'm looking for opinions here.. The next major Zope 2 release and perhaps the next major Zope 3 release will support the loading of packages and (for Zope 2) Products from Python "Egg" files. See http://peak.telecommunity.com/ DevCenter/PythonEggs for an overview. This provides the following benefits: - A packaging pattern that includes standardized metadata which extends existing distutils patterns. - A mechanism to find "certain kinds" of packages (via egg "entry points"). This is important for Zope 2 because it means we can make the use of the Products package namespace optional.. Products needn't be installed into "Products" IOW. - Simpler installation (more than one product can exist in a single egg file). - Dependencies between "distributions" (different egg files) may exist within the standard metadata, and the egg loading machinery can detect whether a dependency is missing. - Egg products can be registered with online catalogs like Cheese Shop, etc very simply. A "spike solution" for egg support in Zope 2 in the form of a product named "Basket" (http://www.plope.com/software/Basket/Basket) already exists. By doing this, we know a lot more about what it will take to put egg support "in to the core". Currently, the Basket product makes the following important assumptions: - There should be no explicit installation step for eggs other than placing the egg on somewhere on Zope's PYTHONPATH. - Packagers can mark their distributions as "non-zip-safe", which causes Basket to automatically unpack the egg file into disk files in a cache directory when Zope starts. This is important for existing products that expect some of their data files to be on disk and not in the egg zipfile. The progenitor of Eggs (Phillip Eby) suggests that this is too implicit. He suggests instead that people who install packages should use a program which implicitly installs packages. The major difference between this and what happens in Basket currently is that packages would be that non-zip-safe packages would be "exploded" at installation time rather than at Zope startup time. The question is this: do you think there should be an explicit "install" step for egg packages/Products or do you think it should be possible to just put eggs on your PYTHONPATH (and perhaps adjust a config file with "requirements")?

5 10

Zope Book 2.7 edition
by Andreas Jung 22 Dec '05

22 Dec '05

Chris, what do you think about moving the current version of the ZB hosted on plope.com back on zope.org. The quickstart page of Zope still points to the 2.6 edition. I would like to get of the 2.6 edition and call it just "Zope Book" + the data of the last modification. Since we can not synchronize Zope release with the Zope Book it would make sense to me to get rid of the version number....I think it is confusing to distinguish between the 2.6 and 2.7 edition (when there is already Zope 2.8) and versions hosted on zope.org vs. plope.com. -aj

3 2