On Fri, Jan 21, 2011 at 04:49:00AM -0500, Chris McDonough wrote: > Here are those issues: > > - Add MANIFEST.in to each Pyramid paster template, and verify its > interaction with setuptools version controlled resource > inclusion. See > https://github.com/Pylons/pyramid/issues#issue/95 ... > If you know something about any of these topics, I'd appreciate any help > with these issues you can provide.
As you can probably tell from my comments on that github issue, I've
been burned a few times by setuptools not including files in packages
I've released on PyPI. My solution, which I offer to your
consideration, is to make sure every package I maintain has a makefile
rule 'distcheck' that ensures my sdists are okay.
The test is basically this:
1. $vcs export the source tree into a temporary directory #1
2. setup.py sdist and extract the .tar.gz into a temporary directory #2
3. diff the two trees (ignoring some files that sdist generates, such as
setup.cfg or $package.egg-info), abort if there are any differences
You can see an example in objgraph's Makefile, e.g.:
http://bazaar.launchpad.net/~mgedmin/objgraph/trunk/view/head:/Makefile#L60
It does a few things more: run the testsuite in temporary directory #2,
builds a second sdist from there, extracts it into a temporary directory
#3 and compares the two again. That's probably overkill and, I think, a
vestige from earlier times when I just compared two sdists, not
realizing that this way I may miss source files not mentioned in the
manifest.
Marius Gedminas
--
Writing setattr hooks properly is a black art. Writing persistent
setattr hooks is more like hearding bees blindfolded...
-- Casey Duncan
signature.asc
Description: Digital signature
