[Zope-dev] Zope Tests: 6 OK
Summary of messages to the zope-tests list. Period Sat Feb 28 12:00:00 2009 UTC to Sun Mar 1 12:00:00 2009 UTC. There were 6 messages: 6 from Zope Tests. Tests passed OK --- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Sat Feb 28 20:23:25 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011205.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Sat Feb 28 20:25:26 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011206.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Sat Feb 28 20:27:28 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011207.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Sat Feb 28 20:29:28 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011208.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Sat Feb 28 20:31:28 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011209.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Sat Feb 28 20:33:28 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011210.html ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.publisher dependencies
On Feb 24, 2009, at 12:59 PM, Shane Hathaway wrote: Jim Fulton wrote: I disagree strongly with many of the assertions made in these articles. (I can't judge the pipeline proposal, since it is only fleshed out in code.) While I do think zope.publisher has some problems, they aren't the same problems that shane sees. What are the problems with zope.publisher as you see it? - It has too many dependencies. Obviously. - It has too much in it. This contributes to the large number of dependencies. - I think the attempt to support multiple protocols through different request types has turned out to be a mistake. I think it was a reasonable approach to try, but I don't think it turned out well, in part because it seems too heavy. Last year, I implemented some Ajax support framework without anything like the complexity that's in the xml-rpc support. I did end up defining a new request marker type to facilitate component lookup, but I was able to do this in a very light- weight way. - It's not well enough documented. While I think there's merit in doing some things at the WSGI level, I remain pretty happy with the publication interface for separatating generic publisher functions from application policies. I which the use of this API was better communicated and understood. A less major complaint is some baggage from the past. There are a number of request features that I never use and tend to forget about. The biggest of these is the special form data unmarshalling and url manipulation support. (I was amused to read in your introduction to your pipeline proposal that people wanted to know the answer to the question: When does Zope respect the :method form variable?. :) Jim -- Jim Fulton Zope Corporation ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Standard request/response API
There's been some discussion recently about separating the interfaces in zope.publisher from the implementations to facilitate other implementations. I think it would be great to standardize request and response APIs. I'd love to see this extend beyond the Zope community. I believe that there have been some moves to try to do this at the WSGI level, although I haven't kept up with the discussion. Speaking for myself, I'd be happy to change my code to comform to a python-standard request API assuming that it had enough in it to adapt it to existing APIs. This might be an excellent project for PyCon. Jim -- Jim Fulton Zope Corporation ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope] chameleon.zpt and zope3.4
This raise a Bad version error: Installing app. The version, 3.4.0, is not consistent with the requirement, 'zope.i18n==3.5'. While: Installing app. Error: Bad version 3.4.0 Le Sunday 01 March 2009 07:35:46 Andreas Jung, vous avez écrit : On 28.02.2009 22:54 Uhr, JeanMichel FRANCOIS wrote: Hi, chameleon require zope.i18n = 3.5. I m using zope3.4 throw KGS, so i have zope.i18n == 3.4. Is there a way to use chameleon on 3.4 ? pin zope.i18n==3.5 within your buildout.cfg -aj ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
