This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gsakkis
Recipients dripton, gsakkis, tarek
Date 2009-02-16.03:18:40
SpamBayes Score 4.11118e-05
Marked as misclassified No
Message-id <1234754337.12.0.607018670773.issue2279@psf.upfronthosting.co.za>
In-reply-to
Content
By an equivalent option in setup() of course. I'm not against the
*functionality* of MANIFEST.in but on that (a) it's a second file you
have to remember to write and maintain in addition to setup.py (b) has
its own ad-hoc syntax instead of python and (c) overlaps in scope with
the package_data and data_files of setup.py.

FWIW I wrote a module that overrides the default build_py and sdist
commands with versions that allow specifying package_data recursively
(while preserving file permissions, unlike the - buggy IMO - behavior of
distutils) so that I can get rid of the MANIFEST.in.
History
Date User Action Args
2009-02-16 03:18:57gsakkissetrecipients: + gsakkis, dripton, tarek
2009-02-16 03:18:57gsakkissetmessageid: <1234754337.12.0.607018670773.issue2279@psf.upfronthosting.co.za>
2009-02-16 03:18:41gsakkislinkissue2279 messages
2009-02-16 03:18:40gsakkiscreate