At 02:00 AM 1/16/2008 +0100, Giampaolo Rodola' wrote: >2008/1/14, Phillip J. Eby <[EMAIL PROTECTED]>: > > At 02:14 AM 1/14/2008 +0100, Giampaolo Rodola' wrote: > > > > (This is a distutils feature and doesn't require setuptools, although > > > > the distutils are a bit trickier to get the tarball to include > > > > everything, as you have to explicitly list in MANIFEST.in anything > > > > that distutils doesn't automatically pick up. > > > > > >Sorry for replying so late. > > >Gently, I would be interested in knowing how can I have distutils to > > >include everything. > > >Currently I've tried to use setup.py sdist but CREDITS, HISTORY, > > >INSTALL and LICENSE files aren't included in the tarball. > > > > http://python.org/doc/2.4.1/dist/manifest.html > >Is there a way to specify that in setup.py?
Not that I'm aware of, no. You just put the MANIFEST.in next to setup.py. The alternative is to use setuptools + source control: setuptools natively picks the files up from SVN or CVS, and there are plugins for several other source control systems including Bazaar, Git, Monotone, and Mercurial, if I recall correctly. (Search PyPI for "setuptools" and the appropriate tool to find the plugin.) (Note that these revision control plugins do NOT require users of your package to have the revision control tool OR the plugin -- it only affects *building* the source distribution, not using it. In fact, it's even possible to make it so your users don't have to have setuptools, although that's not the default setup.) _______________________________________________ Distutils-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/distutils-sig
