January 2006 - Zope-Dev

buildbot failure in Zope trunk 2.4 Windows 2000 zc-bbwin6
by buildbot＠zope.com 27 Jan '06

27 Jan '06

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: 2909 Blamelist: anguenot,dobe,hdima,jim,oestermeier,rykomats,sidnei,tim_one,tseaver,yuppie BUILD FAILED: failed failed slave lost sincerely, -The Buildbot

1 0

Zope tests: 8 OK
by Zope tests summarizer 26 Jan '06

26 Jan '06

Summary of messages to the zope-tests list. Period Wed Jan 25 12:01:01 2006 UTC to Thu Jan 26 12:01:01 2006 UTC. There were 8 messages: 8 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2_6-branch Python-2.1.3 : Linux From: Zope Unit Tests Date: Wed Jan 25 21:03:17 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004098.html Subject: OK : Zope-2_6-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Wed Jan 25 21:04:47 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004099.html Subject: OK : Zope-2_7-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Wed Jan 25 21:06:17 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004100.html Subject: OK : Zope-2_7-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Wed Jan 25 21:07:47 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004101.html Subject: OK : Zope-2_8-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Wed Jan 25 21:09:17 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004102.html Subject: OK : Zope-2_8-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Wed Jan 25 21:10:48 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004103.html Subject: OK : Zope-2_9-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Wed Jan 25 21:12:18 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004104.html Subject: OK : Zope-trunk Python-2.4.2 : Linux From: Zope Unit Tests Date: Wed Jan 25 21:13:48 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004105.html

1 0

Zope tests: 8 OK
by Zope tests summarizer 25 Jan '06

25 Jan '06

Summary of messages to the zope-tests list. Period Tue Jan 24 12:01:01 2006 UTC to Wed Jan 25 12:01:01 2006 UTC. There were 8 messages: 8 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2_6-branch Python-2.1.3 : Linux From: Zope Unit Tests Date: Tue Jan 24 21:03:08 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004090.html Subject: OK : Zope-2_6-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Tue Jan 24 21:04:39 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004091.html Subject: OK : Zope-2_7-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Tue Jan 24 21:06:09 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004092.html Subject: OK : Zope-2_7-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Tue Jan 24 21:07:39 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004093.html Subject: OK : Zope-2_8-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Tue Jan 24 21:09:09 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004094.html Subject: OK : Zope-2_8-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Tue Jan 24 21:10:39 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004095.html Subject: OK : Zope-2_9-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Tue Jan 24 21:12:09 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004096.html Subject: OK : Zope-trunk Python-2.4.2 : Linux From: Zope Unit Tests Date: Tue Jan 24 21:13:40 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004097.html

1 0

Zope - PERFORMANCE PROBLEMS
by Vári Béla 24 Jan '06

24 Jan '06

Dear Sir/Madam! I'm writing on behalf of KFKI ISYS Information Systems Ltd. which is the most decisive part of the biggest system integrator company in Hungary. We have a client where we have used Zope Application Server since 1st of January 2004. We made a continuous expansion in last 2 years so at the moment we have more than 100 users who use the system day by day. Related to this big user number we blundered a big performance problem which couldn't be solved by ourselves, so we need a person who is very expert in Zope and has a lot of experiences in the fine tuning and parametering of Zope. This situation is a really big problem to our client and for us, so we need an emergency help - personal consultancy or support - A.S.A.P. Please send me your suggestions how we can get in. Some additional information about our environment: 1. Apache: Apache/1.3.27 (Linux/SuSE) 2. Zope: (Zope 2.6.1 (source release, python 2.1, linux2) [SuSE Linux], python 2.1.3, linux2) 3. PsyCopg: 1.1.12 4. Python: 2.1.3 (#1, Mar 28 2003, 06:28:54) [GCC 3.3 20030226 (prerelease) (SuSE Linux)] 5. FastCGI: 2.4.0 6. PostGreSQL: (PostgreSQL) 7.3.9 7. SERVER Configuration: SuSE Linux 8.2, RAM 1 GByte, 2,4 GHz I'm waiting for your response. Yours Sincerely, Zoltán PINCZÉS Project Manager KFKI ISYS Information Systems Ltd. H-1134 Budapest, Hungary Tüzér utca 39-41 Phone: +36-1-452-1311, +36-1-452-1300 Fax: +36-1-236-6790 Mobile: +36-70-452-1302 E-mail: ZPinczes(a)kfki-isys.hu

2 1

Zope tests: 8 OK
by Zope tests summarizer 24 Jan '06

24 Jan '06

Summary of messages to the zope-tests list. Period Mon Jan 23 12:01:02 2006 UTC to Tue Jan 24 12:01:02 2006 UTC. There were 8 messages: 8 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2_6-branch Python-2.1.3 : Linux From: Zope Unit Tests Date: Mon Jan 23 21:02:48 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004082.html Subject: OK : Zope-2_6-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Mon Jan 23 21:04:18 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004083.html Subject: OK : Zope-2_7-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Mon Jan 23 21:05:48 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004084.html Subject: OK : Zope-2_7-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Mon Jan 23 21:07:18 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004085.html Subject: OK : Zope-2_8-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Mon Jan 23 21:08:48 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004086.html Subject: OK : Zope-2_8-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Mon Jan 23 21:10:19 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004087.html Subject: OK : Zope-2_9-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Mon Jan 23 21:11:49 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004088.html Subject: OK : Zope-trunk Python-2.4.2 : Linux From: Zope Unit Tests Date: Mon Jan 23 21:13:19 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004089.html

1 0

Zope tests: 8 OK
by Zope tests summarizer 23 Jan '06

23 Jan '06

Summary of messages to the zope-tests list. Period Sun Jan 22 12:01:01 2006 UTC to Mon Jan 23 12:01:01 2006 UTC. There were 8 messages: 8 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2_6-branch Python-2.1.3 : Linux From: Zope Unit Tests Date: Sun Jan 22 21:03:13 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004074.html Subject: OK : Zope-2_6-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Sun Jan 22 21:04:43 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004075.html Subject: OK : Zope-2_7-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Sun Jan 22 21:06:14 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004076.html Subject: OK : Zope-2_7-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Sun Jan 22 21:07:44 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004077.html Subject: OK : Zope-2_8-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Sun Jan 22 21:09:14 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004078.html Subject: OK : Zope-2_8-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Sun Jan 22 21:10:44 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004079.html Subject: OK : Zope-2_9-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Sun Jan 22 21:12:14 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004080.html Subject: OK : Zope-trunk Python-2.4.2 : Linux From: Zope Unit Tests Date: Sun Jan 22 21:13:44 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004081.html

1 0

December release post-mortem
by Jim Fulton 23 Jan '06

23 Jan '06

Now that I've had a week or so to recover from making the Zope 3 releases, I'd like to look at how we did on our first timed releases. Of course, the releases didn't happen in December. In fact, the Zope 2 Windows release still hasn't happened. That we were late isn't a great surprise, given that this was our first timed release. The beginning of the release cycle was delayed because people didn't really realize/remember that we needed to freeze by November 1. The release was delayed past December in large part due to problems found with the Zope 3 Twisted server. In retrospect, I should have accepted these, made ZServer the default and marked the twisted server experimental. Instead, I spent 2 weeks thinking the resolution only needed a few more hours of work. I should have known better. I'm disappointed that the people pushing the Twisted server didn't provide more help during this period, but it was a holiday time and one of the main drivers, Stephan, warned way in advance that we shouldn't be finishing a release during a holiday period. Of course, we should have been finishing the release in early December. In the future, if someone introduces a major change, they *must* be committed to be available to deal with issues that arise during the release cycle. Perhaps we need to pick different release dates to avoid holidays. Stephan has suggested moving the dates up to November/May rather than December/June. And then there are the Windows releases. Making Zope 2 windows releases is very painful and there don't seem to be many people willing to help. We've avoided the pain for Zope 3 by being less ambitious. We let distutils do most of the work. The result is that making a windows release takes minutes and is highly automated, but the experience for the end user is less than ideal, Many would rightfully argue that it is inadequate. What we need is a release process that is as easy as the Zope 3 windows release process and produces a result as usable as the Zope 2 windows release. I'm not sure exactly what the answer is, but I am sure we need to take a fresh approach. Whatever approach we take needs to be highly automated and must not require a lot of specialized Windows expertise. I think that packaging is a significant challenge to our release process. The Zope 2 release was complicated by the use of zpkg. The zpkg system was developed to allow us to decouple the Zope 3 repository and releases. It was too painful to mold the repository to fleeting release decisions. We wanted people to put experimental and add-on applications in the repository so that they would be tested as we rapidly evolved things. While zpkg was crucial for the last 3 releases, I don't think it provides the best long-term approach. Rather than extracting a release from a larger repository tree, I think it would be better, going forward, to assemble a release from smaller individual repository trees or from releases. This is feasible because: - Python is finally growing a packaging system with eggs, - buildbot provides a mechanism for getting things tested without putting everything in a single repository, and - the new test runner's layer makes it feasible to define independent functional tests for packages. We have begun to see Zope 3 decomposed into separate projects knit together via svn:externals. I'd like to see that trend continue and to perhaps switch to making the knitting process use eggs, I'd like to leverage eggs to make the release process much simpler. It should be easy for people to make releases so that there could easily be multiple distributions aimed at different needs and expectations. As part of this decomposition, we need to make zope.app much smaller. Early in Zope 3 development, I proposed a simple rule for organization of the repository: Anything that depended on zope.app went in zope.app. Anything else went in zope. If there was doubt, put it in zope.app. I think that served us well at the time, but I think we've moved beyond that, I'd like to migrate most of zope.app elsewhere. Zope 2.10 should not include zope.app. Note that I'm banking heavily on eggs without personally having worked with them much. I'm very hopeful that we can make them work for us. In the end, I consider the "December" release to be largely successful, given the challenges. These were some of my reactions to this first attempt at time-based releases. What do other folks think? Given that the Zope Foudation will be formed during this next release cycle, I think this is a good time to take stock and think about how to move forward, 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

15 52

[ZPublisher] specifiying 'charset' for the content-type header
by Andreas Jung 23 Jan '06

23 Jan '06

The following usecase is not handled correctly by Zope: When you call a PythonScript returning a Python unicode string then the ZPublisher/HTTPResponse code will convert the unicode response string using HTTPResponse.default_encoding to a Python string. The default encoding is configurable through zope.conf (zpublisher_default_encoding key). This works fine unless you change the encoding to utf-8. In this case Zope sends out UTF8 content without specifying the encoding in the content-type header. I propose the following changes: - Zope adds content-type: text/plain|html when no content-type is specified by the application. In this case we would add 'charset=<DEFAULT_ENCODING> - if the application specfies a content-type header then we would add the charset only if it is undefined Objections? Andreas

2 11

Zope tests: 8 OK
by Zope tests summarizer 22 Jan '06

22 Jan '06

Summary of messages to the zope-tests list. Period Sat Jan 21 12:01:01 2006 UTC to Sun Jan 22 12:01:01 2006 UTC. There were 8 messages: 8 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2_6-branch Python-2.1.3 : Linux From: Zope Unit Tests Date: Sat Jan 21 21:02:20 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004066.html Subject: OK : Zope-2_6-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Sat Jan 21 21:03:50 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004067.html Subject: OK : Zope-2_7-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Sat Jan 21 21:05:20 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004068.html Subject: OK : Zope-2_7-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Sat Jan 21 21:06:51 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004069.html Subject: OK : Zope-2_8-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Sat Jan 21 21:08:21 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004070.html Subject: OK : Zope-2_8-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Sat Jan 21 21:09:51 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004071.html Subject: OK : Zope-2_9-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Sat Jan 21 21:11:21 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004072.html Subject: OK : Zope-trunk Python-2.4.2 : Linux From: Zope Unit Tests Date: Sat Jan 21 21:12:51 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004073.html

1 0

Zope tests: 8 OK
by Zope tests summarizer 21 Jan '06

21 Jan '06

Summary of messages to the zope-tests list. Period Fri Jan 20 12:01:02 2006 UTC to Sat Jan 21 12:01:02 2006 UTC. There were 8 messages: 8 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2_6-branch Python-2.1.3 : Linux From: Zope Unit Tests Date: Fri Jan 20 21:02:02 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004058.html Subject: OK : Zope-2_6-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Fri Jan 20 21:03:32 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004059.html Subject: OK : Zope-2_7-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Fri Jan 20 21:05:02 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004060.html Subject: OK : Zope-2_7-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Fri Jan 20 21:06:32 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004061.html Subject: OK : Zope-2_8-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Fri Jan 20 21:08:02 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004062.html Subject: OK : Zope-2_8-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Fri Jan 20 21:09:33 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004063.html Subject: OK : Zope-2_9-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Fri Jan 20 21:11:03 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004064.html Subject: OK : Zope-trunk Python-2.4.2 : Linux From: Zope Unit Tests Date: Fri Jan 20 21:12:33 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004065.html

1 0