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 tarek
Recipients gsakkis, tarek
Date 2009-02-17.22:48:49
SpamBayes Score 2.5716421e-05
Marked as misclassified No
Message-id <1234910943.54.0.180344443434.issue5302@psf.upfronthosting.co.za>
In-reply-to
Content
I am no in favor of MANIFEST.in removal because I find it very
convenient to define what is included in a package  and I rarely use
package_data or data_files. So I am -1 on its deprecation.

That said, having a mechanism to include directory recursively sounds
good. And people using this wouldn't have to maintain a MANIFEST.in.

Overall, I don't see a problem of having both ways.

Maybe some kind of plugin system could be created so people can
implement their own way to get a file list. I am thinking here about
the feature in setuptools that builds the file list using .svn,
so you don't have to define anything at all.

In any case, for the glob in data_files, how do you express this
MANIFEST.in line ?

recursive-include directory/subdir *.py *.txt
History
Date User Action Args
2009-02-17 22:49:03tareksetrecipients: + tarek, gsakkis
2009-02-17 22:49:03tareksetmessageid: <1234910943.54.0.180344443434.issue5302@psf.upfronthosting.co.za>
2009-02-17 22:48:49tareklinkissue5302 messages
2009-02-17 22:48:49tarekcreate