On http://docs.pylonshq.com/pyramid/dev/narr/project.html#creating-the-project the documentation reads "By default, setup.py sdist does not place non-Python-source files in generated tarballs.".
We have had the same issue in Pylons back then and decided that it's worth creating a MANIFEST.in file reading:
recursive-include foo/static *
recursive-include foo/templates *
Please at least add to the documentation that such a MANIFEST.in file helps distributing a complete application. I honestly don't see the reason not to include templates and static files in a Pyramid-based application because it will probably not work.
My preferred solution is to include such a MANIFEST.in as we did in Pylons.
I second this in the strongest possible terms. Relying on setuptools version control support breaks down when
MANIFEST.in works always.
Can anyone describe (or point me to a link that describes) the interaction between MANIFEST.in and setuptools autoinclusion-by-version-control-status?
I have never used the "autoinclusion-by-version-control-status" feature. The MANIFEST.in is a description of files that should get included in a Python package although they are not actual Python files. See: http://docs.python.org/distutils/sourcedist.html#specifying-the-files-to-distribute
Here's the Setuptools official documentation.
My experience with it leads me to summarize: setup.py sdist includes all of
MANIFEST.in files are now included in the renderings of each paster template in Pyramid: 47442fb