June 2009 - Zope-Dev

Zope Tests: 8 OK
by Zope Tests Summarizer 10 Jun '09

10 Jun '09

Summary of messages to the zope-tests list. Period Tue Jun 9 12:00:00 2009 UTC to Wed Jun 10 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Tests passed OK --------------- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Tue Jun 9 20:51:20 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-June/011907.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Tue Jun 9 20:53:22 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-June/011908.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Tue Jun 9 20:55:22 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-June/011909.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Tue Jun 9 20:57:24 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-June/011910.html Subject: OK : Zope-trunk Python-2.6.1 : Linux From: Zope Tests Date: Tue Jun 9 20:59:24 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-June/011911.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Tue Jun 9 21:01:24 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-June/011912.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Tue Jun 9 21:03:24 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-June/011913.html Subject: OK : Zope-trunk-alltests Python-2.6.1 : Linux From: Zope Tests Date: Tue Jun 9 21:05:25 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-June/011914.html

1 0

Re: [Zope-dev] [Checkins] SVN: zope.app.publisher/trunk/ To make browsers update their caches of resources immediately when the
by Stephan Richter 10 Jun '09

10 Jun '09

On Tuesday 09 June 2009, Wolfgang Schnerring wrote: > To make browsers update their caches of resources immediately when the > resource changes, the absolute URLs of resources can now be made to > contain a hash of the resource's contents, so it will look like > /++noop++12345/@@/myresource instead of /@@/myresource. > > - Implemented an AbsoluteURL adapter that computes a hash of the > resource's contents and inserts that into the URL. - Content hashes will be > cached in memory, except when in developer mode - Introduced a ++noop++ > traverser that simply throws away the path segment - Wrote a bit of > documentation about resources Mmmh, this looks like a lot of extra code to get behavior that is served better with different tools. Have you looked at z3c.versionedresource and z3c.traverser? Both of those should solve these type of use cases well. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter"

5 5

Who uses request.getPositionalArguments()?
by Wolfgang Schnerring 10 Jun '09

10 Jun '09

Hello, I've stumbled over this by accident, but it seems that getPositionalArguments() in zope.publisher.base.BaseRequest always returns an empty value (at least, there are no tests in which it has a non-empty value), and it is also not overridden by any of the request subclasses in zope.publisher. I still haven't quite wrapped my head around the whole publishing machinery, but this strikes me as a little strange, nonetheless. Could somebody enlighten me why this is so? Thanks, Wolfgang

4 5

Zope Tests: 8 OK
by Zope Tests Summarizer 09 Jun '09

09 Jun '09

Summary of messages to the zope-tests list. Period Mon Jun 8 12:00:00 2009 UTC to Tue Jun 9 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Tests passed OK --------------- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Mon Jun 8 20:45:41 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-June/011899.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Mon Jun 8 20:47:50 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-June/011900.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Mon Jun 8 20:49:50 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-June/011901.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Mon Jun 8 20:51:50 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-June/011902.html Subject: OK : Zope-trunk Python-2.6.1 : Linux From: Zope Tests Date: Mon Jun 8 20:53:50 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-June/011903.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Mon Jun 8 20:55:55 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-June/011904.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Mon Jun 8 20:57:55 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-June/011905.html Subject: OK : Zope-trunk-alltests Python-2.6.1 : Linux From: Zope Tests Date: Mon Jun 8 20:59:57 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-June/011906.html

1 0

Zope Tests: 8 OK
by Zope Tests Summarizer 08 Jun '09

08 Jun '09

Summary of messages to the zope-tests list. Period Sun Jun 7 12:00:00 2009 UTC to Mon Jun 8 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Tests passed OK --------------- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Sun Jun 7 20:45:01 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-June/011891.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Sun Jun 7 20:47:01 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-June/011892.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Sun Jun 7 20:49:02 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-June/011893.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Sun Jun 7 20:51:09 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-June/011894.html Subject: OK : Zope-trunk Python-2.6.1 : Linux From: Zope Tests Date: Sun Jun 7 20:53:10 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-June/011895.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Sun Jun 7 20:55:10 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-June/011896.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Sun Jun 7 20:57:11 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-June/011897.html Subject: OK : Zope-trunk-alltests Python-2.6.1 : Linux From: Zope Tests Date: Sun Jun 7 20:59:12 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-June/011898.html

1 0

Zope Tests: 8 OK
by Zope Tests Summarizer 07 Jun '09

07 Jun '09

Summary of messages to the zope-tests list. Period Sat Jun 6 12:00:00 2009 UTC to Sun Jun 7 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Tests passed OK --------------- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Sat Jun 6 20:48:17 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-June/011883.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Sat Jun 6 20:50:19 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-June/011884.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Sat Jun 6 20:52:19 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-June/011885.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Sat Jun 6 20:54:23 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-June/011886.html Subject: OK : Zope-trunk Python-2.6.1 : Linux From: Zope Tests Date: Sat Jun 6 20:56:25 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-June/011887.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Sat Jun 6 20:58:25 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-June/011888.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Sat Jun 6 21:00:26 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-June/011889.html Subject: OK : Zope-trunk-alltests Python-2.6.1 : Linux From: Zope Tests Date: Sat Jun 6 21:02:27 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-June/011890.html

1 0

Odd header-handling behavior of zope.publisher.http.HTTPRequest
by Jim Fulton 06 Jun '09

06 Jun '09

I'll start by saying this is my fault. :( The HTTPRequest.getHeader method will return any environment variable, not just headers. I expect this was a lazy way to handle the odd-ball headers, content-type and content-length (envirnment variables CONTENT_TYPE and CONTENT_LENGTH), which don't have an "HTTP_" prefix in the environment. I think this implementation is rather lame. What's worse, it has a test, testHeader that actually tests the lamosity. I suggest we switch to a tighter behavior. I'd be wildly surprised and disappointed if any apps depended on the lose behavior. If no one objects, I'll file an issue. (I don't think there's anything urgent about this.) Jim -- Jim Fulton Zope Corporation

1 0

Zope Tests: 7 OK, 1 Failed
by Zope Tests Summarizer 06 Jun '09

06 Jun '09

Summary of messages to the zope-tests list. Period Fri Jun 5 12:00:00 2009 UTC to Sat Jun 6 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Test failures ------------- Subject: FAILED (failures=1) : Zope-trunk Python-2.6.1 : Linux From: Zope Tests Date: Fri Jun 5 20:53:00 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-June/011879.html Tests passed OK --------------- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Fri Jun 5 20:44:48 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-June/011875.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Fri Jun 5 20:46:56 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-June/011876.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Fri Jun 5 20:48:59 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-June/011877.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Fri Jun 5 20:50:59 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-June/011878.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Fri Jun 5 20:55:00 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-June/011880.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Fri Jun 5 20:57:01 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-June/011881.html Subject: OK : Zope-trunk-alltests Python-2.6.1 : Linux From: Zope Tests Date: Fri Jun 5 20:59:01 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-June/011882.html

1 0

release zope.testing?
by Wolfgang Schnerring 06 Jun '09

06 Jun '09

Hello, I've recently fixed two bugs in zope.testing that I find annoying on an almost daily basis (commandline option -1 doesn't work and readline is broken in pdb). Could someone review the changes on the trunk and cut a release of zope.testing? Thanks, Wolfgang

2 1

RFC: Site -> Locus
by Martijn Faassen 05 Jun '09

05 Jun '09

Hi there, We have a concept of "Site" in the Zope Toolkit, along with SiteManager and the like. What this concept allows us to do is locally register components. Most typically this is used for local utilities such as a catalog. During traversal, a thread-local is set with the current site, so that code that looks up a compoment will check the current site(s) before falling back on the global component registry. The word "site" has bothered myself and others for some time. It doesn't really have the right connotations for random programmers; when you hear site you think about website, and that's not really what this implies. The reason we called it site I think has to do with the idea that we expected Zope-based web sites to be applications with a lot of local components. I'm interested in refactoring zope.site to split it into two packages: one that has the pure site-based logic with minimal dependencies, and support to easily test with sites, and the other with dependencies on zope.container. While thinking about this, I figured this might be a good opportunity to rename the word 'site' to something better. I propose we use the word 'Locus' instead of 'Site'. This word doesn't have a lot of connotations in the web programming world, and people can guess by simply looking at the word it might have something to do with *local* components. It's also short. It's also a synonym of the word site. The dictionary says: "a place, a locality" and "the scene of any event or action". I think that works quite well. Two possible options for moving forward with this: * create a zope.locus package that contains the core locus support. It only speaks in terms of "locus" and doesn't use the word "site" * zope.locuscontainer will have the container support surrounding sites. * zope.site becomes a backwards compatible but deprecated package that does 'from .. import .. as' to keep 'getSite' and 'setSite' and such around. The package itself will be deprecated and people will be encouraged to depend on zope.locus (or zope.locuscontainer, but that will be rare). The other plan: * we fold the locus support into zope.component. This is assuming that the dependencies for Locus can be kept to a bare minimum (no ZODB dependencies either). * we add the LocusContainer support to zope.container directly; since it already uses zope.component this isn't a problem * zope.site is still a backwards compatible package (that depends on zope.container and zope.component, which it already does). The second plan is my favorite if it is possible dependency-wise and zope.component doesn't take on new dependencies. I think support for local components could very well be part of zope.component conceptually. It would allow us to eliminate one package (zope.site) without introducing any new packages (the other plan increases the amount of packages by one, trading zope.site for zope.locuscontainer). What do people think about: * the idea of renaming Site to Locus * the plan for refactoring? Regards, Martijn

15 42