[Zope-dev] Visibility of policy changes: Was: [Checkins] SVN: zope.app.security/trunk/ keep trunk version at 0. Update changes
On 09/11/2009 05:58 PM, Martijn Faassen wrote: Fred Drake wrote: On Fri, Sep 11, 2009 at 8:53 AM, Martijn Faassen faas...@startifact.com wrote: So, could you please follow this policy for ZTK packages in SVN? I suspect it would help if packages that are part of the ZTK have that indicated somewhere convenient, like near where the version number is specified in the setup.py file. Possibly with a link to the ZTK release policies. When making changes, we're often considering the relevant packages in isolation or in the context of our own applications, so a pointer to additional policies that apply is helpful. That's a good idea. The extreme version of this reminder would to mark it in a lot of places in the package - in every python file and in setup.py near the version and near the dependencies listing and every aspect that could possibly be affected by ZTK policy. That is unworkable. I figured a reference to the ZTK policies on the top of the setup.py would be enough to remind people. I've just committed these changes. I've also taken the liberty to update the ZTK policy to say that this should be done. (other steering group members can call me back if they don't like this policy change :) I'm happy with that change, except that it might be worthwhile to announce policy changes in a separate thread. Christian -- Christian Theune · c...@gocept.com gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Visibility of policy changes: Was: [Checkins] SVN: zope.app.security/trunk/ keep trunk version at 0. Update changes
Hi there, Christian Theune wrote: I'm happy with that change, except that it might be worthwhile to announce policy changes in a separate thread. Good point. I'll do that in the future; please remind again if it doesn't happen. Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Zope Tests: 8 OK
Summary of messages to the zope-tests list. Period Thu Sep 17 12:00:00 2009 UTC to Fri Sep 18 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: Thu Sep 17 20:44:25 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-September/012568.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Thu Sep 17 20:46:25 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-September/012569.html Subject: OK : Zope-2.12 Python-2.4.6 : Linux From: Zope Tests Date: Thu Sep 17 20:48:25 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-September/012570.html Subject: OK : Zope-2.12-alltests Python-2.4.6 : Linux From: Zope Tests Date: Thu Sep 17 20:50:26 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-September/012571.html Subject: OK : Zope-2.12 Python-2.6.2 : Linux From: Zope Tests Date: Thu Sep 17 20:52:26 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-September/012572.html Subject: OK : Zope-2.12-alltests Python-2.6.2 : Linux From: Zope Tests Date: Thu Sep 17 20:54:26 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-September/012573.html Subject: OK : Zope-trunk Python-2.6.2 : Linux From: Zope Tests Date: Thu Sep 17 20:56:26 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-September/012574.html Subject: OK : Zope-trunk-alltests Python-2.6.2 : Linux From: Zope Tests Date: Thu Sep 17 20:58:26 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-September/012575.html ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Visibility of policy changes: Was: [Checkins] SVN: zope.app.security/trunk/ keep trunk version at 0. Update changes
On Friday 18 September 2009, Christian Theune wrote: I've also taken the liberty to update the ZTK policy to say that this should be done. (other steering group members can call me back if they don't like this policy change :) I'm happy with that change, except that it might be worthwhile to announce policy changes in a separate thread. Sounds good to me too, but I think the setup.py file is sufficient. Regards, Stephan -- Entrepreneur and Software Geek Google me. Zope Stephan Richter ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Visibility of policy changes: Was: [Checkins] SVN: zope.app.security/trunk/ keep trunk version at 0. Update changes
On 09/18/2009 02:04 PM, Stephan Richter wrote: On Friday 18 September 2009, Christian Theune wrote: I've also taken the liberty to update the ZTK policy to say that this should be done. (other steering group members can call me back if they don't like this policy change :) I'm happy with that change, except that it might be worthwhile to announce policy changes in a separate thread. Sounds good to me too, but I think the setup.py file is sufficient. I'm not sure I understand your comment correctly. The setup.py doesn't generally need touching. My goal is to keep developers updated on changing policies. Whereas the setup.py change is a one-time thing that allows developers to identify which policy set is valid for a given package. Christian -- Christian Theune · c...@gocept.com gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Visibility of policy changes: Was: [Checkins] SVN: zope.app.security/trunk/ keep trunk version at 0. Update changes
On 09/18/2009 09:21 AM, Martijn Faassen wrote: Hi there, Christian Theune wrote: I'm happy with that change, except that it might be worthwhile to announce policy changes in a separate thread. Good point. I'll do that in the future; please remind again if it doesn't happen. I'll try to. I'll record that in the documentation about decisions. -- Christian Theune · c...@gocept.com gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Visibility of policy changes: Was: [Checkins] SVN: zope.app.security/trunk/ keep trunk version at 0. Update changes
Christian Theune wrote: On 09/18/2009 02:04 PM, Stephan Richter wrote: On Friday 18 September 2009, Christian Theune wrote: I've also taken the liberty to update the ZTK policy to say that this should be done. (other steering group members can call me back if they don't like this policy change :) I'm happy with that change, except that it might be worthwhile to announce policy changes in a separate thread. Sounds good to me too, but I think the setup.py file is sufficient. I'm not sure I understand your comment correctly. The setup.py doesn't generally need touching. I think there was some misunderstanding. I understood Christian to mean I shouldn't announce ZTK policy changes hidden in some thread. If there is new/changed policy we should announce it in a new thread so that people can pick up on it. I'm not sure we can *always* do this. For instance, I just edited the guidelines for when a package should be in the ZTK or not slightly, but it's not really a major policy change. I hope the SVN changelog is enough for this. Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] z3c.hashedresource and cache response headers
Hi, We're trying to make an integration of z3c.hashedresource into Grok. While working on it we wondered how and where people using z3c.hashedresource set the caching headers for the resources referenced by the URLs generated by z3c.hashedresource. A few random thoughts about this: * zope.browserresource.file.FileResource will set cache response headers that are more or less hardcoded. Do people just use these values? * You probably only want to set aggressive cache response headers for resources that are referred to by the URLs generated by z3c.hashedresource. Maybe it is an idea to set these headers in the ++noop++ namespace handler? (although the name noop really isn't suitable anymore then - maybe it could be ++cache++ or something). Any ideas about this? regards, jw ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] z3c.hashedresource and cache response headers
On Friday 18 September 2009, Jan-Wijbrand Kolman wrote: While working on it we wondered how and where people using z3c.hashedresource set the caching headers for the resources referenced by the URLs generated by z3c.hashedresource. I think I solved that in z3c.versionedresource. Regards, Stephan -- Entrepreneur and Software Geek Google me. Zope Stephan Richter ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] z3c.hashedresource and cache response headers
Hi Stephan, Stephan Richter wrote: On Friday 18 September 2009, Jan-Wijbrand Kolman wrote: While working on it we wondered how and where people using z3c.hashedresource set the caching headers for the resources referenced by the URLs generated by z3c.hashedresource. I think I solved that in z3c.versionedresource. /me looks If I understand it correctly, you solved the cache response header issue by subclassing the resource and resource factory implementations of zope.app.publisher.browser. I guess setting cache response headers for resources could actually be factored out of the resource implementation. z3c.versionedresource could then make use of that as well. Hmmm, there's actually an older package called z3c.responseheader that does something in that direction - it wouldn't work for resources though as they set the cache headers themselves in the GET() and HEAD() methods. Would it be a good idea to remove setting the cache headers from the zope.app.publisher.browser resource implementations and make that more pluggable? z3c.versionedresource could then probably get rid of the resource subclasses, right? If people think this is a good idea, I could have a look into it.. regards, jw ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Proposal: Determining packages which are in the ZTK
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This is from a note I sent yesterday to the ZTK steering group (Martijn, Christian, Jim, Stephan), proposing criteria for removing packages from the ZTK. Martijn has already updated the docs to reflect some of the criteria: I figured I would throw the rest out for discussion: - - If a ZTK package isn't used by at least Zope2 and Grok, it probably isn't getting the love needed to stay at an appropriate quality level to meet the ZTK goals. Given that the Zope2 developers have as an explicit goal removing dependencies on *any* zope.app.* package, I obviously believe that such packages should not be part of the ZTK. - - Any package which doesn't have real narrative documentation checked into its 'docs' subdirectory, or a commitment from a maintainer to create such docs, should be on probation. - - Any package which depends on a zope.* package which is *not* part of the ZTK should itself be removed from the ZTK. - - As a corollary, any package which depends on any other probationary package is automatically probationary itself. - - (A little more speculative) Any package which doesn't have one or more clearly-identified maintainers should be probationary. - - Packages which remain in the probationary status for a given period (three months? six?) should be removed from the ZTK. The overall goal here is to keep the ZTK as coherent as possible, and avoid bitrot by focusing on the packages which are in active use by more than one project. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFKs6zm+gerLs4ltQ4RAuBrAKCmtecUClk+EmaNvyuXS+A6seGLpwCfSKtS Kx/kzSRzZ5r28MahjjXX9Zo= =b4sb -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Proposal: rip twisted integration out of Zope2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Two modules do a really complicated and ugly conditional import dance to try and make twisted availabe as an alternative to ZServer. I propose we nuke that dance on the Zope trunk: at this point, we should prefer to do WSGI well, and leave integrating a specific external server out of the core. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFKs63C+gerLs4ltQ4RAqGKAKDNnQDs4+2lr7V+H4/e44Rva1pjBgCgrjeC IKkSjsSZIVsBpP3BR1O3PIg= =k8h6 -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Proposal: Determining packages which are in the ZTK
On Sep 18, 2009, at 11:53 AM, Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This is from a note I sent yesterday to the ZTK steering group (Martijn, Christian, Jim, Stephan), proposing criteria for removing packages from the ZTK. Martijn has already updated the docs to reflect some of the criteria: I figured I would throw the rest out for discussion: - - If a ZTK package isn't used by at least Zope2 and Grok, it probably isn't getting the love needed to stay at an appropriate quality level to meet the ZTK goals. Given that the Zope2 developers have as an explicit goal removing dependencies on *any* zope.app.* package, I obviously believe that such packages should not be part of the ZTK. - - Any package which doesn't have real narrative documentation checked into its 'docs' subdirectory, or a commitment from a maintainer to create such docs, should be on probation. - - Any package which depends on a zope.* package which is *not* part of the ZTK should itself be removed from the ZTK. - - As a corollary, any package which depends on any other probationary package is automatically probationary itself. - - (A little more speculative) Any package which doesn't have one or more clearly-identified maintainers should be probationary. - - Packages which remain in the probationary status for a given period (three months? six?) should be removed from the ZTK. The overall goal here is to keep the ZTK as coherent as possible, and avoid bitrot by focusing on the packages which are in active use by more than one project. Sounds interesting. Do you happen to have a list of packages that would be affected by these rules? Gary ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Proposal: Move Products.five.form out to a new package
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Most of the remaining zope.app dependencies in the Zope2 trunk are related to Products.five.form. I propose moving all that code out to a new package, e.g. 'five.forms', which can be included by anybody who uses that code. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFKs653+gerLs4ltQ4RAhHwAKDHlDoq2u0DkPM9J1dP0163ieVJpgCdEU7M mtZzqX+J2VgKprh1NLJE9Uw= =6jSP -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Proposal: Determining packages which are in the ZTK
On Fri, Sep 18, 2009 at 11:53 AM, Tres Seaver tsea...@palladion.com wrote: - - Any package which depends on a zope.* package which is *not* part of the ZTK should itself be removed from the ZTK. +1 - - As a corollary, any package which depends on any other probationary package is automatically probationary itself. +0 - - (A little more speculative) Any package which doesn't have one or more clearly-identified maintainers should be probationary. -0 -Fred -- Fred L. Drake, Jr.fdrake at gmail.com Chaos is the score upon which reality is written. --Henry Miller ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Proposal: quit importing zope.app.schema.vocabulare in Products.Five
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Yuppie: I don't know what the purpose of the following checkin was: http://svn.zope.org/Zope/trunk/?rev=85827view=rev but the tests all pass if I rip out the import, and Zope starts. I don't know what code in Zope2 expects the ZopeVocabularyRegistry to be registered. Can you remember what needed it? Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFKs7BY+gerLs4ltQ4RAoyqAKCeZs/TZPwSN6xkg28TtbidhAHy0gCeMvrA 5zQ9YCnVfETtj3m0XPRsRY8= =oDgZ -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Proposal: rip twisted integration out of Zope2
On 18.09.09 17:56, Tres Seaver wrote: Two modules do a really complicated and ugly conditional import dance to try and make twisted availabe as an alternative to ZServer. Can you explain a bit more? I propose we nuke that dance on the Zope trunk: at this point, we should prefer to do WSGI well, and leave integrating a specific external server out of the core. You mean dropping the ZServer and Medusa? Andreas attachment: lists.vcf___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Proposal: rip twisted integration out of Zope2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andreas Jung wrote: On 18.09.09 17:56, Tres Seaver wrote: Two modules do a really complicated and ugly conditional import dance to try and make twisted availabe as an alternative to ZServer. Can you explain a bit more? I propose we nuke that dance on the Zope trunk: at this point, we should prefer to do WSGI well, and leave integrating a specific external server out of the core. You mean dropping the ZServer and Medusa? No, I mean dropping the experimental twisted alternative. ZServer is battle-hardened, well-supported, and shouldn't need to be pulled out: it allows for standalone use of Zope without any external integration. IIRC, the twisted integration code was added because Jim wanted us to get out of the server business. At this point, I think that folks wanting an alternative to ZServer should focus on using WSGI to integrate with the server of their choice; we should make that as easy / smooth as possible, and ditch the (undermaintained / icky / old) twisted integration. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFKs7Ll+gerLs4ltQ4RAgCrAJwK7m7KWh3gKEUQOn4Hor4I82SRhQCginN2 649lwD37oNTiDv9nePR5spI= =kcsj -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Proposal: rip twisted integration out of Zope2
On 18.09.09 18:18, Tres Seaver wrote: Andreas Jung wrote: On 18.09.09 17:56, Tres Seaver wrote: Two modules do a really complicated and ugly conditional import dance to try and make twisted availabe as an alternative to ZServer. Can you explain a bit more? I propose we nuke that dance on the Zope trunk: at this point, we should prefer to do WSGI well, and leave integrating a specific external server out of the core. You mean dropping the ZServer and Medusa? No, I mean dropping the experimental twisted alternative. ZServer is battle-hardened, well-supported, and shouldn't need to be pulled out: it allows for standalone use of Zope without any external integration. IIRC, the twisted integration code was added because Jim wanted us to get out of the server business. At this point, I think that folks wanting an alternative to ZServer should focus on using WSGI to integrate with the server of their choice; we should make that as easy / smooth as possible, and ditch the (undermaintained / icky / old) twisted integration. I totally agree with your observation and consider the Twisted integration as mission-failed. Nothing objections from my side. If you don't see objections by others, just go ahead. Andreas attachment: lists.vcf___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Proposal: Determining packages which are in the ZTK
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gary Poster wrote: Sounds interesting. Do you happen to have a list of packages that would be affected by these rules? Sure: all the zope.app packages. They have effectively been in probationary status for a while now; I'm proposing to remove them completely from the ZTK. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFKs7NP+gerLs4ltQ4RAnzaAJ0e/oLpeO6/TcBEggPjO03DoDNazgCgj0z5 ws36yQbTkTJ3rHobw1szIqg= =Wy/f -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Proposal: rip twisted integration out of Zope2
On Fri, Sep 18, 2009 at 1:23 PM, Andreas Jung li...@zopyx.com wrote: IIRC, the twisted integration code was added because Jim wanted us to get out of the server business. At this point, I think that folks wanting an alternative to ZServer should focus on using WSGI to integrate with the server of their choice; we should make that as easy / smooth as possible, and ditch the (undermaintained / icky / old) twisted integration. I totally agree with your observation and consider the Twisted integration as mission-failed. Nothing objections from my side. If you don't see objections by others, just go ahead. IIRC, the twisted integration actually runs a WSGI server. But then again, my memory fooled me more than once this week alone. -- Sidnei ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Proposal: Move Products.five.form out to a new package
On Fri, Sep 18, 2009 at 5:59 PM, Tres Seaver tsea...@palladion.com wrote: Most of the remaining zope.app dependencies in the Zope2 trunk are related to Products.five.form. I propose moving all that code out to a new package, e.g. 'five.forms', which can be included by anybody who uses that code. +1, I'd call it five.formlib to make it clear it wraps zope.formlib. Hanno ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] z3c.hashedresource and cache response headers
On Friday 18 September 2009, Jan-Wijbrand Kolman wrote: Would it be a good idea to remove setting the cache headers from the zope.app.publisher.browser resource implementations and make that more pluggable? z3c.versionedresource could then probably get rid of the resource subclasses, right? Right, I probably sub-classed because there was no other way. I would welcome a hook of any kind. It seems silly to me that we cannot easily adjust such fundamental settings. Regards, Stephan -- Entrepreneur and Software Geek Google me. Zope Stephan Richter ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Proposal: Determining packages which are in the ZTK
On Fri, Sep 18, 2009 at 6:20 PM, Tres Seaver tsea...@palladion.com wrote: Sure: all the zope.app packages. They have effectively been in probationary status for a while now; I'm proposing to remove them completely from the ZTK. I'd like to leave any zope.app.* package in the under-review section as long as one is a dependency of a ZTK package. This includes testing dependencies. We need to care and maintain those packages as long as we depend on them. Otherwise we could move them to the dependency section, so we'd make sure to have a complete working set. Take for example zope.traversing [1] which has a major bunch of test dependencies. I'd like the process to be: first refactor the tests, then drop the dependency. Hanno [1] http://svn.zope.org/zope.traversing/trunk/setup.py?view=markup ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Proposal: rip twisted integration out of Zope2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andreas Jung wrote: On 18.09.09 18:18, Tres Seaver wrote: Andreas Jung wrote: On 18.09.09 17:56, Tres Seaver wrote: Two modules do a really complicated and ugly conditional import dance to try and make twisted availabe as an alternative to ZServer. Can you explain a bit more? I propose we nuke that dance on the Zope trunk: at this point, we should prefer to do WSGI well, and leave integrating a specific external server out of the core. You mean dropping the ZServer and Medusa? No, I mean dropping the experimental twisted alternative. ZServer is battle-hardened, well-supported, and shouldn't need to be pulled out: it allows for standalone use of Zope without any external integration. IIRC, the twisted integration code was added because Jim wanted us to get out of the server business. At this point, I think that folks wanting an alternative to ZServer should focus on using WSGI to integrate with the server of their choice; we should make that as easy / smooth as possible, and ditch the (undermaintained / icky / old) twisted integration. I totally agree with your observation and consider the Twisted integration as mission-failed. Nothing objections from my side. If you don't see objections by others, just go ahead. He's dead, Jim. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFKs+O2+gerLs4ltQ4RAmZMAKDT/7LqJj3YH+l81G+KcjOBvdIF5ACfd7gs XKXYCFS6z5SW9MyohX+BE8U= =S/Sa -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Proposal: quit importing zope.app.schema.vocabulare in Products.Five
Hi Tres! Tres Seaver wrote: I don't know what the purpose of the following checkin was: http://svn.zope.org/Zope/trunk/?rev=85827view=rev See https://mail.zope.org/pipermail/zope-dev/2008-April/031691.html but the tests all pass if I rip out the import, and Zope starts. I don't know what code in Zope2 expects the ZopeVocabularyRegistry to be registered. Can you remember what needed it? A wrong import in CMFCalendar did mask the problem, but I just fixed that and now you can see some CMF tests failing if that import is removed in Five. Cheers, Yuppie ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Proposal: quit importing zope.app.schema.vocabulare in Products.Five
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 yuppie wrote: Hi Tres! Tres Seaver wrote: I don't know what the purpose of the following checkin was: http://svn.zope.org/Zope/trunk/?rev=85827view=rev See https://mail.zope.org/pipermail/zope-dev/2008-April/031691.html but the tests all pass if I rip out the import, and Zope starts. I don't know what code in Zope2 expects the ZopeVocabularyRegistry to be registered. Can you remember what needed it? A wrong import in CMFCalendar did mask the problem, but I just fixed that and now you can see some CMF tests failing if that import is removed in Five. Having tests fail becuase of a removed import-for-side-effects doesn't give me a good feeling about the quality of the tests. At any rate, if there is a real feature needed by Zope2 to function correctly, then we should move it from zope.app.schema to zope.schema, and make it possible to configure cleanly (instead of via side effects). (Later) OK, I have copied the ZopeVocabularyRegistry from zope.app.schema.vocabulary into a new module, Products.Five.schema, renaming it to Zope2VocabularyRegistry. I arranged to get it installed insside Five's initialize(). I updated the failing CMFDefault and CMFCalendar doctests to import and install that registry in a new 'setUp', and clear it in 'tearDown'. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFKtA2v+gerLs4ltQ4RAi5oAKCXNuwoRQF4BxJzh2spyKrb88qayQCg2QLO ByRVppF1cxkij17H9m8Xirc= =cTYR -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] SVN: Zope/trunk/ Cloned ``ZopeVocabularyRegistry`` from ``zope.app.schema``.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hanno Schlichting wrote: Wouldn't it make sense to move the VocabularyRegistry class into zope.schema instead of forking it? Nope -- the implementation uses zope.component, which would create a cycle. The fork is really fine here: it is truly only six lines of code (plus tests, docstrings, module headers, etc.). My tests are clearer and more comprehensive, too. :) Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFKtA8E+gerLs4ltQ4RAmSeAJ9Nd2FrgfS3t1OAkeA/KaOW4/IV+ACfRTXQ YDYMnUC9s2MS5CIs5qt3wb4= =2hPX -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Proposal: quit importing zope.app.schema.vocabulare in Products.Five
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tres Seaver wrote: yuppie wrote: Hi Tres! Tres Seaver wrote: I don't know what the purpose of the following checkin was: http://svn.zope.org/Zope/trunk/?rev=85827view=rev See https://mail.zope.org/pipermail/zope-dev/2008-April/031691.html but the tests all pass if I rip out the import, and Zope starts. I don't know what code in Zope2 expects the ZopeVocabularyRegistry to be registered. Can you remember what needed it? A wrong import in CMFCalendar did mask the problem, but I just fixed that and now you can see some CMF tests failing if that import is removed in Five. Having tests fail becuase of a removed import-for-side-effects doesn't give me a good feeling about the quality of the tests. At any rate, if there is a real feature needed by Zope2 to function correctly, then we should move it from zope.app.schema to zope.schema, and make it possible to configure cleanly (instead of via side effects). (Later) OK, I have copied the ZopeVocabularyRegistry from zope.app.schema.vocabulary into a new module, Products.Five.schema, renaming it to Zope2VocabularyRegistry. I arranged to get it installed insside Five's initialize(). I updated the failing CMFDefault and CMFCalendar doctests to import and install that registry in a new 'setUp', and clear it in 'tearDown'. Ugh, I have the sinking feeling that this fix needs to be backported to the 2.12 branch before we get to a release. Andreas, it is a pretty small change, actually, and removes any dependency on zope.app.schema: can I merge it? Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFKtBDs+gerLs4ltQ4RAsjhAJ4qeIgTNzoVwncQ+X1KsYkMyzwQbQCdEtr3 wRM8xKIvrL1dq8JIy7DA5HI= =Vy1V -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
