> (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. 2007/12/20, Phillip J. Eby <[EMAIL PROTECTED]>: > At 02:26 PM 12/20/2007 +0100, Giampaolo Rodola' wrote: > >Oh, I'm sorry, > >yestarday night it was very late (5:00 AM) and I completely > >misunderstood what you said. > >Thanks for your help, I'm going to rename the tarball. > > It will be better for you in general if you just use "setup.py sdist" > to generate your tarballs, as they will then have the right name, and > also will include the distutils PKG-INFO. > > (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. Setuptools on the > other hand will automatically include anything that's under revision > control in your project, unless you use MANIFEST.in to tell it *not* > to. CVS+SVN support is built in, plugins for various other revision > control systems can be found on PyPI.) > > _______________________________________________ Distutils-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/distutils-sig
