toutpt wrote: > I have read some documentation and discuss about it with kiorky who think > that manifest.in must not be used and is error prone. I'm agree with him > that you can easily forgot some extension like jpeg or what ever.
Currently I've standardized my code to the following (replace 'collective' with your own namespace if applicable) MANIFEST.in ----------- include *.txt recursive-include docs * recursive-include collective * ------------ This applies to the directory if setup.py, You usually don't add *.jpg in that root-directory. I've thrown out:global-exclude *.pyc as these shouldn't be committed in the first place. And if no *.pyc exist setuptools gives unnecessary warnings for that. > So I have check the plone code and their is no manifest.in. Do that means > it must not to be used ? I personally would love to see more questions like these: which is better "A" or "B"?; or to "B" or not to "B"? One of the things that make it hard to learn and understand is the lack of consistenty. One package does this and another does it differently. (just look at the titles of GS-profiles in portal_setup, this becomes problematic of you have for example two ReferenceBrowserwidget-packages) Personnally, I like "explicit is better than implicit" For quite some time I didn't know about the implicit defaults setuptools/distribute/.. takes, and its dependency on .svn-folders for example. -- Greets, WouterVH _______________________________________________ Product-Developers mailing list [email protected] http://lists.plone.org/mailman/listinfo/product-developers
