November 2007 - Zope-Dev

Zope Tests: 5 OK
by Zope Tests Summarizer 05 Nov '07

05 Nov '07

Summary of messages to the zope-tests list. Period Sun Nov 4 13:00:00 2007 UTC to Mon Nov 5 13:00:00 2007 UTC. There were 5 messages: 5 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Sun Nov 4 20:50:29 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-November/008596.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Sun Nov 4 20:52:00 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-November/008597.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Sun Nov 4 20:53:30 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-November/008598.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Sun Nov 4 20:55:00 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-November/008599.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Sun Nov 4 20:56:30 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-November/008600.html

1 0

Re: [Checkins] SVN: zc.i18n/trunk/setup.py vb
by Benji York 04 Nov '07

04 Nov '07

From the check-in messages: > Changed: > U zc.i18n/trunk/setup.py > - version = '0.5.2', > + version = '0.6.0', As best I can tell, http://svn.zope.org/*checkout*/Sandbox/philikon/foundation/releasing-softwa… was accepted as policy (Jim endorsed it and no one maintained public objections). Therefore, anyone editing the trunk version numbers needs add "dev" (no hyphen) on the end. Thanks. -- Benji York Senior Software Engineer Zope Corporation

5 5

Re: [Checkins] SVN: zope.testbrowser/trunk/ Fix bug introduced in 3.4.1 that created incompatible tracebacks in doctests.
by Benji York 04 Nov '07

04 Nov '07

Stephan Richter wrote: > On Saturday 03 November 2007, Benji York wrote: >> Log message for revision 81431: >> Fix bug introduced in 3.4.1 that created incompatible tracebacks in >> doctests. This neccesitated adding a patched mechanize to the source tree; >> patches have been sent to the mechanize project. > > Yeah, you are right, I changed the errors since the last version of > mechanize -- 0.1.7b -- throws the wrong error. I should have used RE > normalizers to fix the problem instead of rewriting the doc tests. I will go > through the packages that are effected and fix that. I don't think normalizers are necessary. Testbrowser should have never raised different exceptions. Probably the best thing to do would be to put the "HTTPError"s back where "httperror_seek_wrapper" is now. > Specifying versions in either the setup.py or buildout.cfg is a really bad > idea because it makes it impossible for people with different KGSs to work on > packages. I certainly see how putting versions in setup.py is bad, but don't understand how versions in buildout.cfg cause problems. Can you explain? > Also, I am not sure that including mechanize in the testbrowser release is a > good idea. What if other packages in my repos also use mechanize, but they > rely on the good and bad things of the released packages? I think this will > end in a big mess. As there's no released version of mechanize that will work, I don't see another option. What alternative do you suggest? (changing cc: to zope-dev) -- Benji York Senior Software Engineer Zope Corporation

1 0

Zope Tests: 5 OK
by Zope Tests Summarizer 04 Nov '07

04 Nov '07

Summary of messages to the zope-tests list. Period Sat Nov 3 13:00:00 2007 UTC to Sun Nov 4 13:00:00 2007 UTC. There were 5 messages: 5 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Sat Nov 3 21:48:17 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-November/008591.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Sat Nov 3 21:49:47 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-November/008592.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Sat Nov 3 21:51:17 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-November/008593.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Sat Nov 3 21:52:48 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-November/008594.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Sat Nov 3 21:54:20 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-November/008595.html

1 0

buildbot failure in Zope trunk 2.4 Windows 2000 zc-bbwin6
by buildbot＠zope.com 03 Nov '07

03 Nov '07

The Buildbot has detected a failed build of Zope trunk 2.4 Windows 2000 zc-bbwin6. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 3123 Blamelist: benji_york,fdrake,fschulze,malthe,regebro,srichter BUILD FAILED: failed test sincerely, -The Buildbot

1 0

Zope Tests: 5 OK
by Zope Tests Summarizer 03 Nov '07

03 Nov '07

Summary of messages to the zope-tests list. Period Fri Nov 2 13:00:00 2007 UTC to Sat Nov 3 13:00:00 2007 UTC. There were 5 messages: 5 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Fri Nov 2 21:52:51 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-November/008586.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Fri Nov 2 21:54:22 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-November/008587.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Fri Nov 2 21:55:52 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-November/008588.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Fri Nov 2 21:57:22 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-November/008589.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Fri Nov 2 21:58:52 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-November/008590.html

1 0

Bad package dependencies
by Chris McDonough 03 Nov '07

03 Nov '07

In summary: - Uploading eggs that have loose install_requires dependencies to the cheeseshop is harmful. - Taking non-Zope-the-appserver deployments into account, I'd be suspicious of any "install_requires" dependency on "zope.configuration" except in a Zope-the-appserver meta-egg. - Same for the [zcml] extra when specifying 'zope.component' in install_requires. - The dependencies of zope.configuration seem not sane, transitively. - The dependencies of zope.component [zcml] seem not sane, transitively (although 'zope.component' without the [zcml] is reasonably sane). Details: I wanted to go use zope.pagetemplate in a small non-Zope project. When I did "easy_install zope.pagetemplate" (from PyPI) into a fresh virtual environment, it installed all of the following eggs: ./zope.pagetemplate-3.4.0-py2.4.egg ./zope.tal-3.4.0-py2.4.egg ./zope.tales-3.4.0-py2.4.egg ./zope.interface-3.4.1-py2.4-macosx-10.3-i386.egg ./zope.i18n-3.4.0-py2.4.egg ./zope.i18nmessageid-3.4.3-py2.4-macosx-10.3-i386.egg ./zope.configuration-3.4.0-py2.4.egg ./zope.component-3.4.0-py2.4.egg ./pytz-2007g-py2.4.egg ./zope.schema-3.4.0-py2.4.egg ./zope.deprecation-3.4.0-py2.4.egg ./zope.proxy-3.4.0-py2.4-macosx-10.3-i386.egg ./zope.security-3.4.0-py2.4-macosx-10.3-i386.egg ./zope.event-3.4.0-py2.4.egg ./zope.deferredimport-3.4.0-py2.4.egg ./zope.testing-3.5.1-py2.4.egg ./zope.location-3.4.0-py2.4.egg ./zope.exceptions-3.4.0-py2.4.egg ./zope.traversing-3.4.0-py2.4.egg ./zope.publisher-3.4.1-py2.4.egg ./zope.app.applicationcontrol-3.4.1-py2.4.egg ./zope.app.testing-3.4.1-py2.4.egg ./zope.size-3.4.0-py2.4.egg ./zope.error-3.5.1-py2.4.egg ./zope.app.security-3.4.0-py2.4.egg ./zope.app.publication-3.4.3-py2.4.egg ./zope.app.folder-3.4.0-py2.4.egg ./zope.app.dependable-3.4.0-py2.4.egg ./zope.app.debug-3.4.0-py2.4.egg ./zope.app.container-3.5.2-py2.4-macosx-10.3-i386.egg ./zope.app.component-3.4.1-py2.4.egg ./zope.app.authentication-3.4.1-py2.4.egg ./zope.annotation-3.4.0-py2.4.egg ./zope.app.appsetup-3.4.1-py2.4.egg ./ZODB3-3.8.0b4-py2.4-macosx-10.3-i386.egg ./zope.app.publisher-3.5.0a2-py2.4.egg ./zope.app.pagetemplate-3.4.0-py2.4.egg ./zope.app.form-3.4.1-py2.4.egg ./zope.app.exception-3.4.1-py2.4.egg ./zope.app.error-3.5.1-py2.4.egg ./zope.app.http-3.4.1-py2.4.egg ./zope.dublincore-3.4.0-py2.4.egg ./zope.datetime-3.4.0-py2.4.egg ./zope.copypastemove-3.4.0-py2.4.egg ./zope.app.broken-3.4.0-py2.4.egg ./zope.filerepresentation-3.4.0-py2.4.egg ./zope.lifecycleevent-3.4.0-py2.4.egg ./zope.dottedname-3.4.2-py2.4.egg ./zope.cachedescriptors-3.4.0-py2.4.egg ./zope.app.zapi-3.4.0-py2.4.egg ./zope.thread-3.4-py2.4.egg ./zope.formlib-3.4.0-py2.4.egg ./zope.app.interface-3.4.0-py2.4.egg ./zope.app.session-3.5.1-py2.4.egg ./zdaemon-2.0.1-py2.4.egg ./ZConfig-2.5-py2.4.egg Once it gets past ZConfig, it then failed with: error: Installed distribution zope.traversing 3.4.0 conflicts with requirement zope.traversing>=3.5.0a1.dev-r78730 The transitive install_requires dependencies of zope.pagetemplate 3.4.0 can't possibly be right, or at least they're much too conservative. The problem starts in the install_requires of zope.i18n: install_requires=['setuptools', 'pytz', 'zope.i18nmessageid', 'zope.component [zcml]', 'zope.configuration', ], zope.i18n should not depend on zope.configuration in install_requires, because it's only used in it's "zcml.py" and if you use it as a library (as opposed to as a Zope plugin) you won't load up any of its zcml; even if "important" stuff gets registered, it's expected that you'll have to do it by hand when it's used as a library. The dependency on 'zope.component [zcml]' is legitimate except for the [zcml] part for the same reason. The install_requires for the zope.pagetemplate setup.py (at least for 3.4.0) should be: install_requires=['setuptools', 'pytz == 2007g', 'zope.i18nmessageid == 3.4.3', 'zope.component == 3.4.0', ], When I build a new zope.i18n (3.4.0) egg with these dependencies, its transitive dependency set when installed is: pytz-2007g-py2.4.egg setuptools-0.6c7-py2.4.egg zope.component-3.4.0-py2.4.egg zope.deferredimport-3.4.0-py2.4.egg zope.deprecation-3.4.0-py2.4.egg zope.event-3.4.0-py2.4.egg zope.i18n-3.4.0-py2.4.egg zope.i18nmessageid-3.4.3-py2.4-macosx-10.3-i386.egg zope.interface-3.4.1-py2.4-macosx-10.3-i386.egg zope.proxy-3.4.0-py2.4-macosx-10.3-i386.egg .. which is acceptable, I think. Once that's done, the additional dependencies imposed by zope.pagetemplate are: zope.pagetemplate zope.tal zope.tales .. and it works as a library: Python 2.4.4 (#1, Oct 17 2007, 20:25:32) [GCC 4.0.1 (Apple Computer, Inc. build 5250)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from zope.pagetemplate.pagetemplatefile import PageTemplate >>> my_pt = PageTemplate() >>> my_pt.write("<html></html>") >>> my_pt() u'<html></html>\n' I ran all unit tests by hand, as opposed to risking false passes due to installations that would come from tests_require when invoked via setup.py test and they work. I've uploaded the revised zope.i18n tarball here: http://dist.repoze.org/zope.i18n-3.4.0.1-repoze.tar.gz The current release of zope.pagetemplate on PyPI just can't be installed via easy_install due to a conflict, probably because somebody uploaded a new egg and some dependency isn't specific enough. Removing the dependency on "zope.configuration" and "zope.component [zcml]" (replacing it with "zope.component") in my case happens to fix that for me temporarily but this is indicative of a larger problem. Distributions made with "install_requires" specifications that do not name a particular "==" version or at least a min-max range should not be uploaded to the cheeseshop (as opposed to a private repository that has a smaller working set and to whom fewer people contribute), because their existence is just pollution for people who try to install them using easy_install. The transitive dependency set will inevitably break over time as new (incompatible) eggs are uploaded, as the Grok folks already know. I think fixing this sort of stuff is important if it's a goal to allow people to use Zope technologies outside of Zope-the-appserver. I'd like to participate by making new releases, but I'm not sure whose toes I'd be stepping on, and I think I'd need guidance from people who understand why things are the way they are now. Maybe we should have a sprint. - C

3 2

Zope on Python 2.5?
by Alexander Limi 03 Nov '07

03 Nov '07

Sorry if this has been asked hundreds of times before — I couldn't find any info on this apart from the Summer of Code project related to Zope 3. Will Zope 2 ever run on Python 2.5, or is that postponed indefinitely? We see an increasing amount of users trying to use Zope 2 with their systems that have Python 2.5 as default. -- Alexander Limi · http://limi.net

17 26

Zope 3 catalog
by Roché Compaan 02 Nov '07

02 Nov '07

Where can one find Zope 3 catalog? Or is it simply zope.index? -- Roché Compaan Upfront Systems http://www.upfrontsystems.co.za

2 3

Zope Tests: 5 OK
by Zope Tests Summarizer 02 Nov '07

02 Nov '07

Summary of messages to the zope-tests list. Period Thu Nov 1 13:00:00 2007 UTC to Fri Nov 2 13:00:00 2007 UTC. There were 5 messages: 5 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Thu Nov 1 21:48:08 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-November/008581.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Thu Nov 1 21:49:38 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-November/008582.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Thu Nov 1 21:51:08 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-November/008583.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Thu Nov 1 21:52:38 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-November/008584.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Thu Nov 1 21:54:09 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-November/008585.html

1 0