plone buildout and Products namespace

Leonardo Rochael leo at enfoldsystems.com
Wed Oct 17 19:50:12 UTC 2007


Not sure this is the right forum to reach those involved with the respective
code...

I've been playing with the plone3_buildout paste template and the recipes
sets up for your buildout. Specifically the plone.recipe.distro buildout,
which is also used by the plone.recipe.plone one for the non-eggified
Products.

Now that Zope officially declares Products to be a namespace, shouldn't we
be setting up these recipes to put these distributed products in a Products
namespace as well?

The change to the recipes is simple enough, just add a Products subdirectory
to each part and an __init__.py declaring the namespace before downloading
and unpacking the products, and in the zope2instance recipe putting
something like:

products =
    ${buildout:directory}/Products <-- notice the capital P
    ${productdistros:location}/Products
    ${plone:products}/Products

The benefit of this is enabling tools that understand python namespace
packages to understand what is happening with the products in a buildout.

One example of such a tool is the PyDEV extensions static code analysis
tool, that scans python files to enable proper code completion.

Would people be interested in such changes to the recipes and to the
ZopeSkel template?
-- 
View this message in context: http://www.nabble.com/plone-buildout-and-Products-namespace-tf4642882s20094.html#a13261545
Sent from the Product Developers mailing list archive at Nabble.com.





More information about the Product-Developers mailing list