Including setuptools_scm as a setup_requires declaration will invoke the setuptools file_finder to automatically include any files found in the SCM (e.g. Git) repository. Thus, the developer doesn't have to maintain a separate manifest (one in a MANIFEST.in and another in the SCM repo) and run the risk of the two being inconsistent.
I believe non-code-files deserves at least a nod to file finders as a more automated solution to the problem of non-code-files.
Thanks for these docs. I was searching for how to handle package data and it took me to http://python-packaging.readthedocs.io/en/latest/non-code-files.html. I followed that technique in one project before I realized there's a more automated way to include such files.
Including setuptools_scm as a
setup_requiresdeclaration will invoke the setuptoolsfile_finderto automatically include any files found in the SCM (e.g. Git) repository. Thus, the developer doesn't have to maintain a separate manifest (one in a MANIFEST.in and another in the SCM repo) and run the risk of the two being inconsistent.I believe non-code-files deserves at least a nod to file finders as a more automated solution to the problem of non-code-files.