[Zope-dev] Component registry simplification leftovers
i was setting up a z3 app with a pau utility, and noticed some strange behavior, which tracked down to, the PluggableAuthentication's getPrincipal method, source below. def getPrincipal(self, id): if not id.startswith(self.prefix): next = queryNextUtility(self, IAuthentication) if next is None: raise PrincipalLookupError(id) return next.getPrincipal(id) id = id[len(self.prefix):] for name, authplugin in self.getAuthenticatorPlugins(): info = authplugin.principalInfo(id) if info is None: continue info.credentialsPlugin = None info.authenticatorPlugin = authplugin principal = interfaces.IFoundPrincipalFactory(info)(self) principal.id = self.prefix + info.id return principal next = queryNextUtility(self, IAuthentication) if next is not None: return next.getPrincipal(self.prefix + id) raise PrincipalLookupError(id) i had setup a local site with a pau with a prefix and an ldap auth, lookups for common groups like zope.EveryBody, zope.Authenticated, would in turn call queryNextUtility. however instead of returning the global site manager's principal registry, it would fail in the utility lookup. digging deeper, the queryNextUtility call is passing in a context of the authentication utility itself, which looks like a throwback to the older IComponentLookup adaptation, instead of the current thread local site manager with bases, thats currently used. When the auth utility is passed to queryNextUtility, the default site manager whose bases are queried is the global site manager, resulting in no utility found. Where as passing context none, gives the expected behavior, of looking up the current local site's bases for the auth utility in the global site manager. it appears to me, that this is a throwback/missed refactoring from jim's merge of the component registry refactoring.. can anyone confirm the analysis and the bug? this pattern is present in multiple places in pluggable auth utility implementation, and also, zope.app.security/zope/app/security/vocabulary.py:219 cheers, kapil ___ 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] Zope3 on Google AppEngine
perhaps too late to help with the sprints, but i got zope3 running on app engine last week http://zope3.appspot.com and http://zope3.appspot.com/tests, and blogged about to http://blog.kapilt.com most of zope.app isn't useable due to persistence or containment and security proxies, but page templates and the publisher work. some fairly minor but pervasive changes (removing some deprecations/bbb code) were needed, and to have space (1000 file limit) to actually develop an application requires stripping the eggs of text and tests. i ended up using the publisher support in zope.publisher (3.5.1+) instead of ore.wsgiapp or lovely.nozodb as it presents a much more minimal dependency set. i'd like to see if i can get some form machinery going underneat the 1000 file limit, and publish a starter tarball for folks interested. i'm uncertain long term what's viable, as their were a number of changes needed, and how best to maintain them. if their suitable for upstream into the zope repository, or just done again for separate releases as gae variant of z3. cheers, kapil On 5/22/08, Jodok Batlogg <[EMAIL PROTECTED]> wrote: > Hi, > > Next week Lovely will be sprinting in New York/San Francisco to get the > Zope3 framework and the first applications running on Google AppEngine. > You're welcome to join us. > Google AppEngine is a perfect match to the transition we at Lovely Systems > made during the last 12 month in "stealth mode". > We're using heavily WSGI and are replacing ZODB within most of our > applications. > Tomorrow we're leaving to New York visiting our friend reco. dobee and I > will be working on getting the component architecture running on AppEngine. > Later next week we'll fly to San Francisco to attend Google I/O and get > even more insight to the technology. > We're open to release lovely.nozodb and the related components in near > future, as usual - just some polishing missing… > Please drop me a note ([EMAIL PROTECTED], batlogg on skype/AIM) or > give me a call (+43 664 9636963) if you want to join us. > > jodok > -- > Lovely Systems, Partner > > phone: +43 5572 908060, fax: +43 5572 908060-77 > Schmelzhütterstraße 26a, 6850 Dornbirn, Austria > _ ___ 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: setuptools extension for buildout old-style tar-balls?
Andreas Jung wrote: lots of old-style Zope products are now available as eggs. However a lot of people still don't work with buildout and need the old-style tar-balls. Does anyone know of a setuptools extension for generating and upload the tar-balls directly from a Products. package? Using the 'sdist' command is not suitable since it includes the 'Products' top-level directory which is not what we want. Not yet, but I would be willing to help with writing one, as I could use one quite regularly. Hanno ___ 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 Tests: 5 OK
Summary of messages to the zope-tests list. Period Sat May 31 11:00:00 2008 UTC to Sun Jun 1 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Tests passed OK --- Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Sat May 31 20:57:13 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009635.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Sat May 31 20:58:43 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009636.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Sat May 31 21:00:14 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009637.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Sat May 31 21:01:44 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009638.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Sat May 31 21:03:15 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009639.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 )
[Zope-dev] setuptools extension for buildout old-style tar-balls?
Hi, lots of old-style Zope products are now available as eggs. However a lot of people still don't work with buildout and need the old-style tar-balls. Does anyone know of a setuptools extension for generating and upload the tar-balls directly from a Products. package? Using the 'sdist' command is not suitable since it includes the 'Products' top-level directory which is not what we want. Andreas -- ZOPYX Ltd. & Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany Web: www.zopyx.com - Email: [EMAIL PROTECTED] - Phone +49 - 7071 - 793376 Registergericht: Amtsgericht Stuttgart, Handelsregister A 381535 Geschäftsführer/Gesellschafter: ZOPYX Limited, Birmingham, UK E-Publishing, Python, Zope & Plone development, Consulting pgpYYwYetJCxy.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 )
