[Zope-dev] Zope Tests: 6 OK
Summary of messages to the zope-tests list. Period Sun Mar 7 12:00:00 2010 UTC to Mon Mar 8 12:00:00 2010 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: Sun Mar 7 20:36:45 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-March/013696.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Sun Mar 7 20:38:45 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-March/013697.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Sun Mar 7 20:40:45 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-March/013698.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Sun Mar 7 20:42:45 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-March/013699.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Sun Mar 7 20:44:45 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-March/013700.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Sun Mar 7 20:46:45 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-March/013701.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] zope.component.zcml and global registry
* 2010-03-04 20:51, Fabio Tranchitella wrote: Committed with tests. If nobody objects, I would like to release a new (bugfix) release of zope.component with the current trunk. This is the relevant entry from the CHANGES.txt file: - The ZCML directives provided by zope.component now register the components in the registry returned by getSiteManager instead of the global registry. This allows the hooking of the getSiteManager method before the load of a ZCML file to register the components in a custom registry. Thanks, Fabio ___ 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] zope.component.zcml and global registry
On Mon, Mar 8, 2010 at 9:18 PM, Fabio Tranchitella kob...@kobold.it wrote: * 2010-03-04 20:51, Fabio Tranchitella wrote: Committed with tests. If nobody objects, I would like to release a new (bugfix) release of zope.component with the current trunk. This is the relevant entry from the CHANGES.txt file: - The ZCML directives provided by zope.component now register the components in the registry returned by getSiteManager instead of the global registry. This allows the hooking of the getSiteManager method before the load of a ZCML file to register the components in a custom registry. Is this a feature release ? Regards, Baiju M ___ 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] zope.component.zcml and global registry
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Baiju M wrote: On Mon, Mar 8, 2010 at 9:18 PM, Fabio Tranchitella kob...@kobold.it wrote: * 2010-03-04 20:51, Fabio Tranchitella wrote: Committed with tests. If nobody objects, I would like to release a new (bugfix) release of zope.component with the current trunk. This is the relevant entry from the CHANGES.txt file: - The ZCML directives provided by zope.component now register the components in the registry returned by getSiteManager instead of the global registry. This allows the hooking of the getSiteManager method before the load of a ZCML file to register the components in a custom registry. Is this a feature release ? It seems arguable either way to me: the old behavior (forcibly populating the global registry instead of the hooked registry) could easily be construed as a bug. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkuVLf8ACgkQ+gerLs4ltQ4dNACgtOjXaYXEZR2kTTsXnyDKGokT zuAAoL/9WZ4RtC4CBq+I7gV4k6iokoRj =Piih -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] vyshakh krishnan wants to chat
--- vyshakh krishnan wants to stay in better touch using some of Google's coolest new products. If you already have Gmail or Google Talk, visit: http://mail.google.com/mail/b-dbd6bff667-b1982e48b6-0879284f0da0a451 You'll need to click this link to be able to chat with vyshakh krishnan. To get Gmail - a free email account from Google with over 2,800 megabytes of storage - and chat with vyshakh krishnan, visit: http://mail.google.com/mail/a-dbd6bff667-b1982e48b6-0879284f0da0a451 Gmail offers: - Instant messaging right inside Gmail - Powerful spam protection - Built-in search for finding your messages and a helpful way of organizing emails into conversations - No pop-up ads or untargeted banners - just text ads and related information that are relevant to the content of your messages All this, and its yours for free. But wait, there's more! By opening a Gmail account, you also get access to Google Talk, Google's instant messaging service: http://www.google.com/talk/ Google Talk offers: - Web-based chat that you can use anywhere, without a download - A contact list that's synchronized with your Gmail account - Free, high quality PC-to-PC voice calls when you download the Google Talk client We're working hard to add new features and make improvements, so we might also ask for your comments and suggestions periodically. We appreciate your help in making our products even better! Thanks, The Google Team To learn more about Gmail and Google Talk, visit: http://mail.google.com/mail/help/about.html http://www.google.com/talk/about.html (If clicking the URLs in this message does not work, copy and paste them into the address bar of your browser). ___ 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] vyshakh krishnan wants to chat
Hi, On 03/08/2010 06:34 PM, vyshakh krishnan wrote: --- vyshakh krishnan wants to stay in better touch using some of Google's coolest new products. This is a mailinglist and you probably have dumped your address book to the invitation system. I've seen a couple of those talk to Zope mailinglists recently. Can you *please* avoid putting mailing list addresses into those systems? 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] zope.component.zcml and global registry
Hi Tres Betreff: Re: [Zope-dev] zope.component.zcml and global registry -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Baiju M wrote: On Mon, Mar 8, 2010 at 9:18 PM, Fabio Tranchitella kob...@kobold.it wrote: * 2010-03-04 20:51, Fabio Tranchitella wrote: Committed with tests. If nobody objects, I would like to release a new (bugfix) release of zope.component with the current trunk. This is the relevant entry from the CHANGES.txt file: - The ZCML directives provided by zope.component now register the components in the registry returned by getSiteManager instead of the global registry. This allows the hooking of the getSiteManager method before the load of a ZCML file to register the components in a custom registry. Is this a feature release ? It seems arguable either way to me: the old behavior (forcibly populating the global registry instead of the hooked registry) could easily be construed as a bug. Probably you have a very different point of view to this changes. Let me explain what I think about that. We have two kind of registries in zope a global/non persistent and local/persistent in local sites. The setSite hooks forces to set the right context for component lookup. Note, I mean component lookup, and not component registry lookup or register components! ZCML based configuration actions are not persistent and can't get registered in a local component registry. This is the reason why we didn't use the hooked getSiteManager method for this configuration actions. What this changes really does is, it allows to set a site which forces to use another site manager which contains a different component registry. I don't think setup another site is the right concept to use another component registry. Probably there should be an explicit call for the IComponents utility in this case. btw, if you like to register actions for another registry then the global registry, there is a concept implemented in z3c.baseregistry. It does exactly what the changes forces to do without the possible sideeffect of register non peristent actions in a local persistent component registry. With some lines of ZCML every action could register it's handler to such another global component registry. e.g. utility component=my.global.Registry provides=zope.component.interfaces.IComponents name=other / zope:registerIn registry=my.global.Registry !-- include your ZCML here -- /zope:registerIn Now, if your site provides the 'other' IComponents utility, your fine and you will get what you need. This concept explicit allows to register components in a component registry and does not invoke a running application in any way. In my point of view, this changes/feature is implemented as simple as possible and not done right. If you configure a system during startup, in our case with ZCML actions, it's really not a good idea to change the running system itself for make this possible. Another point, reloading ZCML actions after a system startup e.g. from the UI is probably not possible anymore. Then we whould have to call setSite(None) and this, on a running system, whould force to loose the local components registry at the same time. But anyway, if nobody objects I'm fine with this changes. I just like to make sure everybody really knows the sideeffects of this changes and hope we're not having problems later with this feature. Regards Roger Ineichen ___ 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] zope.component.zcml and global registry
On Mon, Mar 8, 2010 at 7:23 PM, Roger d...@projekt01.ch wrote: Another point, reloading ZCML actions after a system startup e.g. from the UI is probably not possible anymore. Then we whould have to call setSite(None) and this, on a running system, whould force to loose the local components registry at the same time. I'm not sure if there's other code that implements this, but if you look at the way I do it in plone.reload [1], you'll notice that it already does an explicit getGlobalSiteManager call and a setSite(None). The site is set again on the next request, when traversing over the local site object. The code also has to minimize the ZODB cache, or the local site will have some cached info that might have been invalidated by the global changes. So I don't see this as a counter argument :) Hanno [1] http://svn.plone.org/svn/plone/plone.reload/trunk/plone/reload/zcml.py ___ 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] zope.component.zcml and global registry
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Roger wrote: Hi Tres Betreff: Re: [Zope-dev] zope.component.zcml and global registry -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Baiju M wrote: On Mon, Mar 8, 2010 at 9:18 PM, Fabio Tranchitella kob...@kobold.it wrote: * 2010-03-04 20:51, Fabio Tranchitella wrote: Committed with tests. If nobody objects, I would like to release a new (bugfix) release of zope.component with the current trunk. This is the relevant entry from the CHANGES.txt file: - The ZCML directives provided by zope.component now register the components in the registry returned by getSiteManager instead of the global registry. This allows the hooking of the getSiteManager method before the load of a ZCML file to register the components in a custom registry. Is this a feature release ? It seems arguable either way to me: the old behavior (forcibly populating the global registry instead of the hooked registry) could easily be construed as a bug. Probably you have a very different point of view to this changes. Let me explain what I think about that. We have two kind of registries in zope a global/non persistent and local/persistent in local sites. The setSite hooks forces to set the right context for component lookup. Note, I mean component lookup, and not component registry lookup or register components! ZCML based configuration actions are not persistent and can't get registered in a local component registry. This is the reason why we didn't use the hooked getSiteManager method for this configuration actions. What this changes really does is, it allows to set a site which forces to use another site manager which contains a different component registry. I don't think setup another site is the right concept to use another component registry. Probably there should be an explicit call for the IComponents utility in this case. btw, if you like to register actions for another registry then the global registry, there is a concept implemented in z3c.baseregistry. It does exactly what the changes forces to do without the possible sideeffect of register non peristent actions in a local persistent component registry. With some lines of ZCML every action could register it's handler to such another global component registry. e.g. utility component=my.global.Registry provides=zope.component.interfaces.IComponents name=other / zope:registerIn registry=my.global.Registry !-- include your ZCML here -- /zope:registerIn Now, if your site provides the 'other' IComponents utility, your fine and you will get what you need. This concept explicit allows to register components in a component registry and does not invoke a running application in any way. In my point of view, this changes/feature is implemented as simple as possible and not done right. If you configure a system during startup, in our case with ZCML actions, it's really not a good idea to change the running system itself for make this possible. Another point, reloading ZCML actions after a system startup e.g. from the UI is probably not possible anymore. Then we whould have to call setSite(None) and this, on a running system, whould force to loose the local components registry at the same time. But anyway, if nobody objects I'm fine with this changes. I just like to make sure everybody really knows the sideeffects of this changes and hope we're not having problems later with this feature. The Highlander model (there can be only one) for ZCML-configured non-persistent component registries is self-limiting. BFG is an existence proof that multiple non-persistent registries, each configured via ZCML, can work and be useful: it allows us to run multiple, unrelated apps within a single process, without mingling their configurations. Note that BFG doesn't use persistent registries at all. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkuVSL4ACgkQ+gerLs4ltQ5HxwCgp9melxb/ZBAer7nPOhh1Lo0b OhsAn0pxFprn3GlC740+pjNSdbNhkHh9 =b3kb -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] z3c.password and tracking failed login attempts
Hi, A while ago I asked some questions and made some suggestions for improving how to track failed login attempts in z3c.password. Most likely these suggestions got buried in now a out-of-sight thread and were never noticed. My suggestion was that making a request for for example a resource could still trigger the account locked errors, where in my opinion only the login attempts themselves should do that. I created a branch of z3c.password..: http://svn.zope.org/z3c.password/branches/jw-noraise-for-irrelevant-requests/ ..that will check for request relevancy as early as possible. All tests pass without modification, but with this change after an account has been locked out requests for for example resources will still work. Additionally I think the code is a tad more readible now. I added a test to demonstrate the specific behaviour. Would any of the z3c.password users/developers object to having this branch merged to the trunk? 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] vyshakh krishnan wants to chat
Christian Theune wrote: This is a mailinglist and you probably have dumped your address book to the invitation system. I've seen a couple of those talk to Zope mailinglists recently. Can you *please* avoid putting mailing list addresses into those systems? Better yet, I wonder if there is some equivalent of robots.txt for email. Domain owners should be able to create and host a file that specifies policies for automated email. Does anyone know of such a standard? Shane ___ 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.password and tracking failed login attempts
Hi Jan Betreff: [Zope-dev] z3c.password and tracking failed login attempts Hi, A while ago I asked some questions and made some suggestions for improving how to track failed login attempts in z3c.password. Most likely these suggestions got buried in now a out-of-sight thread and were never noticed. My suggestion was that making a request for for example a resource could still trigger the account locked errors, where in my opinion only the login attempts themselves should do that. I created a branch of z3c.password..: http://svn.zope.org/z3c.password/branches/jw-noraise-for-irrel evant-requests/ ..that will check for request relevancy as early as possible. All tests pass without modification, but with this change after an account has been locked out requests for for example resources will still work. Additionally I think the code is a tad more readible now. I added a test to demonstrate the specific behaviour. Would any of the z3c.password users/developers object to having this branch merged to the trunk? Adam is on holiday this week. I'm sure he will take a look at the branch next monday. Regards Roger Ineichen 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] zope.component.zcml and global registry
Hi Hanno Betreff: Re: [Zope-dev] zope.component.zcml and global registry On Mon, Mar 8, 2010 at 7:23 PM, Roger d...@projekt01.ch wrote: Another point, reloading ZCML actions after a system startup e.g. from the UI is probably not possible anymore. Then we whould have to call setSite(None) and this, on a running system, whould force to loose the local components registry at the same time. I'm not sure if there's other code that implements this, but if you look at the way I do it in plone.reload [1], you'll notice that it already does an explicit getGlobalSiteManager call and a setSite(None). The site is set again on the next request, when traversing over the local site object. The code also has to minimize the ZODB cache, or the local site will have some cached info that might have been invalidated by the global changes. So I don't see this as a counter argument :) There is allways a way to do things ;-) Tweak a running system itself for reload configuration is probably not the best one. As more as I think about what Fabio changed and what really happens, I think it's just a missing API which splits the ZCML action configuration and the running system into different parts. But since you're telling that reload patterns can work with this changes, I think this is good news. Regards Roger Ineichen Hanno [1] http://svn.plone.org/svn/plone/plone.reload/trunk/plone/reload/zcml.py ___ 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 )
