David Glick wrote: > > On Sep 20, 2010, at 4:01 AM, Raphael Ritz <[email protected]> > wrote: > >> Kees Hink wrote: >>> In order to use Products.sqlpfgadapter [1] with collective.megaphone, some >>> additional (zcml) setup is needed that i'd like to keep in a separate >>> product. >>> >>> I'd like to use the "collective.megaphone" namespace [2], >>> "collective.megaphone.sqlstorage" seems a good name for the product. Would >>> you >>> agree? >> As far as I understand http://www.python.org/dev/peps/pep-0382/ >> and setuptools and friends you cannot do that since >> collective.megaphone is already defined as non-namespace package. > > As far as setuptools goes you can do it as long as all of the packages only > have the namespace initialization boilerplate in their __init__.py.
Sorry for not being clear. That's exactly what I meant with "collective.megaphone is already defined as non-namespace package" If it were a ns package - meaning containing only namespace initialization boilerplate - then that would be OK but it contains regular code, so it's not a ns package and you can't use it as such. Raphael > But I tried to set up collective.megaphone like this (for another add-on), > and was running into problems loading the ZCML from the correct place. So I > don't think it will work reliably. > > I ended up naming my package/distribution collective.megaphonecicerolookup > >> As others suggested before consider something like >> collective.megaphonesql >> > > +1 > > > ---------- > David Glick > Web Developer > [email protected] > 206.286.1235x32 > > Groundwire: You Are Connected > http://groundwire.org _______________________________________________ Product-Developers mailing list [email protected] http://lists.plone.org/mailman/listinfo/product-developers
