-----BEGIN PGP SIGNED MESSAGE-----
On 3 Oct 2006, at 05:40, Wichert Akkerman wrote:
I am updating my OpenId authentication plugin to be a standard python
package instead of a Zope product and am hitting a problem with
PluggableAuthService.all_meta_types: it filters the registered types
on a list of meta_types in the Products package. Since my package
in plone.openid that effectively removes it.
Is there any reason to do that filtering? Since the meta_types are
registered at runtime we already know that the package is present.
What we get from the plugin registration isn't the structure expected
as a return value from all_meta_types. The plugin registration only
gives us a sequence of meta_type strings. So in effect we are not
filtering, we're simply converting to a suitable data structure that
is found in Products.meta_types, and those are then returned.
I haven't worked with products that are standard Python packages, but
even if you cannot find them in Products.meta_types (why not I
wonder? Is this a bug in the mechanism that enables Python package
products?) I am assuming there has to be some place where you could
look up their product information programmatically. all_meta_types
could be extended to look in more than one place for this product
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
-----END PGP SIGNATURE-----
Zope-PAS mailing list