Re: [Zope-dev] Branches finished for merging.
--On 27. April 2006 00:17:18 +0200 Lennart Regebro [EMAIL PROTECTED] wrote: On 4/26/06, Andreas Jung [EMAIL PROTECTED] wrote: What are the possible risks of those changes? What is the goal of this branch? Integration as an optional feature or replacement of ZPublisher/ZServer? The direct goal of this is to make it more pluggable, so that we can introduce twisted or zope.publisher as alternatives. Twisted, so that we can write new servers for Zope2, and zope.publisher, so that we can closer to the goal of being able to run both Zope3 and Zope2 software under the same server. That's fine The long term goal is to replace ZServer/ZPublisher with whatever Zope3 uses, which at that point in time most likely will be twisted/zope.publisher, to tighten the Z2/Z3 integration, and reduce the amount of code we need to maintain. Getting rid of ZServer is a fine goal but as long as Twisted is much slower (from what I've heard) ZServer has to stay (ZServer is not subject to be deprecated at this time). The risks is that somehow we introduce some subtle behavioural change that isn't tested for. I would love to see the stuff tested with the major frameworks (CMF 2, Plone + CPS) before it will be merged into the trunk. The traversal refactoring means that the role checking is now done after each traversal step, instead of intermingled with it. The functionality should be the same, but perhaps there is some untested special case when it changes. We have had much larger incompatibility changes in earlier major releases though. The WSGI refactoring may mean that somebody using internal features of ZServer might need to change something. Also it means that what the publish_module() method expect as parameters will change. I have no problems with the traversal refactoring..that sound sane. -aj -- ZOPYX Ltd. Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany Web: www.zopyx.com - Email: [EMAIL PROTECTED] - Phone +49 - 7071 - 793376 E-Publishing, Python, Zope Plone development, Consulting pgpReGz3xMqf3.pgp Description: PGP signature ___ 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] Branches finished for merging.
On 4/27/06, Andreas Jung [EMAIL PROTECTED] wrote: Getting rid of ZServer is a fine goal but as long as Twisted is much slower (from what I've heard) ZServer has to stay (ZServer is not subject to be deprecated at this time). ZServer will remain the default for now, and it will not be deprecated unless the community wishes so. I'm guessing the community will want to sooner or later. ;-) Twisted is slower, but how much of a difference that makes in real life applications I don't know. The server is in itself not a very big performance eater in Zope. There is of course also the option to use something else that can use WSGI, like for example zope.server, which is much cleaner than ZServer, and probably therefore easier to maintain. The risks is that somehow we introduce some subtle behavioural change that isn't tested for. I would love to see the stuff tested with the major frameworks (CMF 2, Plone + CPS) before it will be merged into the trunk. Sure. The traversal refactoring means that the role checking is now done after each traversal step, instead of intermingled with it. The functionality should be the same, but perhaps there is some untested special case when it changes. We have had much larger incompatibility changes in earlier major releases though. The WSGI refactoring may mean that somebody using internal features of ZServer might need to change something. Also it means that what the publish_module() method expect as parameters will change. I have no problems with the traversal refactoring..that sound sane. -- Lennart Regebro, Nuxeo http://www.nuxeo.com/ CPS Content Management http://www.cps-project.org/ ___ 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] Branches finished for merging.
--On 27. April 2006 10:33:19 +0200 Lennart Regebro [EMAIL PROTECTED] wrote: On 4/27/06, Andreas Jung [EMAIL PROTECTED] wrote: Getting rid of ZServer is a fine goal but as long as Twisted is much slower (from what I've heard) ZServer has to stay (ZServer is not subject to be deprecated at this time). ZServer will remain the default for now, and it will not be deprecated unless the community wishes so. I'm guessing the community will want to sooner or later. ;-) Sure, we all want that (but not for the sake of slower performance) :-) Twisted is slower, but how much of a difference that makes in real life applications I don't know. The server is in itself not a very big performance eater in Zope. There is of course also the option to use something else that can use WSGI, like for example zope.server, which is much cleaner than ZServer, and probably therefore easier to maintain. Can I only repeat the rumors I've heard from the integration of Twisted in Zope 3. So we won't give up an efficient implementation of a core component..that's just what I wanted to say. Having some benchmarks would be nice. And btw. thanks for your work :-) Andreas -- ZOPYX Ltd. Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany Web: www.zopyx.com - Email: [EMAIL PROTECTED] - Phone +49 - 7071 - 793376 E-Publishing, Python, Zope Plone development, Consulting pgpYJSXJUkIIm.pgp Description: PGP signature ___ 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] Reminder: Feature Freeze May 1
--On 21. April 2006 08:55:26 -0400 Jim Fulton [EMAIL PROTECTED] wrote: Don't forget that the feature freeze for the June release is May 1! That is only 10 days away! New features should be check in in a *stable* form by then. While we won't necessarily do a beta release then, anything checked in for the new release must be ready for a beta release when it is checked into the trunk. We need agree on a release schedule. Perhaps we should agree on a schedule on IRC? Andreas -- ZOPYX Ltd. Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany Web: www.zopyx.com - Email: [EMAIL PROTECTED] - Phone +49 - 7071 - 793376 E-Publishing, Python, Zope Plone development, Consulting pgp9rADlLTs2w.pgp Description: PGP signature ___ 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] Zope 2.10: Remaining tasks
The feature freeze date for the June release is only days away. It was planned to be May 1st, but due to lots of pending branches, we might let it slip for a *couple* of days (not more!). I've compiled a rough list of outstanding tasks for Zope 2.10: http://www.zope.org/Wikis/DevSite/Projects/Zope2.10/Tasks Please complete and/or correct this list. It is up to the release managers (Stephan, Andreas) and the Pope to decide the exact feature freeze date, but I would suggest that we start merging those branches real soon. I'll try to complete my work today. Philipp ___ 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 2.10: Remaining tasks
Philipp von Weitershausen wrote: The feature freeze date for the June release is only days away. It was planned to be May 1st, but due to lots of pending branches, we might let it slip for a *couple* of days (not more!). I've compiled a rough list of outstanding tasks for Zope 2.10: http://www.zope.org/Wikis/DevSite/Projects/Zope2.10/Tasks Please complete and/or correct this list. It is up to the release managers (Stephan, Andreas) and the Pope to decide the exact feature freeze date, but I would suggest that we start merging those branches real soon. But, of course, only the branches that are ready should be merged. Where ready means the author has a reasonable expectation that a beta release can be made after after the merge. It would be helpful if the authors of the branches listed on: http://www.zope.org/Wikis/DevSite/Projects/Zope2.10/Tasks would update the page by either deleting their branch or giving a realistic estimate of when it will be ready. It's a good idea to be conservative. The next release after this one is not very far away (November). I propose we exclude any branches that don't have an estimate by Monday. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ 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] request.debug needed for Zope 3 ZPT engine
Several components that we'd like to use in Zope2, such as the SequenceEngine from Zope3, use the Zope 3 ZPT engine to render some things. (This has nothing to do with Zope 2 using or not using the Zope 3 ZPT engine.) The Zope 3 ZPT engine, in particular zope.app.pagetemplate.ViewPageTemplateFile, makes the assumption that 'request' properly implements IBrowserRequest. The Zope 2 request doesn't implement all of it, but it's close enough to make most of the Zope 3 stuff work. ViewPageTemplateFile, however, uses the 'debug' property of the request (it's specified in the request interface). This 'debug' property is an instance of DebugFlags and basically is a debugging switch for ZPT and other things. The Zope 2 request obviously doesn't have this 'debug' property. In the past we've usually added the necessary properties to the Zope 2 request in such cases. We could do this again, however: The Zope 2 request allows form data access through the __getattr__ protocol (the Zope 3 request does this through __getitem__). request.debug would shadow a potential 'debug' form variable and might break applications that make use of this form variable (I would expect there are at least a couple). Note that the obvious workaround is to use request.form['debug'] or request.cookies['debug'], depending on where you get the variable from. I would even say that this should be the preferred way of getting to form variables or cookies. But given the antiqueness of the Zope 2 API and no truly encouraged way of accessing things, there is to be expected code that relies on request.debug being the form variable. I would still vote for introducing the change. At some point (perhaps even in Zope 2.10), we'll want to use more and more of the Zope 3 ZPT engine. This problem would reoccur then. I'm therefore going to introduce the change on the zope33-port branch, as it is necessary for getting Five 1.5 (see Five's zope33-port branch) and Zope 2 to work with Zope 3.3. Comments? Philipp ___ 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] Re: request.debug needed for Zope 3 ZPT engine
Philipp von Weitershausen wrote: Several components that we'd like to use in Zope2, such as the SequenceEngine from Zope3, That's meant to say SequenceWidget, and we already *are* using it in Five, so not supporting request.debug would mean dropping support for SequenceWidget or having to reimplement it. Philipp ___ 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] Re: Zope 2.10: Remaining tasks
Jim Fulton wrote: It would be helpful if the authors of the branches listed on: http://www.zope.org/Wikis/DevSite/Projects/Zope2.10/Tasks would update the page by either deleting their branch or giving a realistic estimate of when it will be ready. It's a good idea to be conservative. I've been able to complete my work tonight. The changes haven't been merged yet for reasons stated on the wiki page (also see http://mail.zope.org/pipermail/zope-dev/2006-April/027408.html). I'll be gone over the weekend and back after (the international) Labour Day. That means I can do the merging of my branches Tuesday or any time after that. Philipp ___ 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 )