[Distutils] Manifests

[Jeremy Hylton]

On Mon, 2004-01-19 at 10:21, Fred L. Drake, Jr. wrote:
> Jeremy Hylton writes:
>  > I think the MANIFEST.in language is a little odd and poorly documented,
>  > but I don't know that it would be any better if I had to write Python
>  > code to achieve the same effect.  Here's a MANIFEST.in for a project I

> I think a lot of milage could be had if there were a way to specify
> additional file extensions that should be copied as part of packages
> along with .py files.  The would certainly be a reasonable 80%
> solution for the packages for which I work on the setup.py files.

Good point!  If we could have that option work for a bunch of commands,
it would help.  We also suffer to get data files copied into
site-packages along with their modules.  If you could just say .xml
files in my modules should get installed just like .py files, life would
be much simpler.

> The next most important improvement would be a way to say the Python
> packages are "over there" in cases where they aren't in the top-level
> directory where the setup.py resides.  I'm thinking of cases where the
> Python packages are located in a src/ or lib/python/ directory.

We've already got that, unless i misunderstand you:  package_dir.  The
package_dir dictionary tells distutils where to find various packages. 
The keys are package names, the values are directories.  The empty
string is provides a default package directory.  See the Zope3 setup.py
for an example.

Jeremy