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 erik.bray
Recipients alexis, eric.araujo, erik.bray, tarek
Date 2011-04-09.18:09:37
SpamBayes Score 9.966685e-10
Marked as misclassified No
Message-id <1302372583.74.0.876049331605.issue11805@psf.upfronthosting.co.za>
In-reply-to
Content
As far as I've been able to tell there is no proposed syntax in the docs specifically for package_data.  The docs for the resources option seems to suggest separating globs with spaces, which would be fine by me (wouldn't allow paths that contain spaces, but that's a bad idea anyways).

I think that allowing one glob string on each line is more readable, but I'm not too attached either way.  Another possibility would be to allow line breaks in the value, for example:

package data = 
    mypackage = templates/*.html
                static/css/*.css

But that's getting a little more complex syntax-wise.

Agreed on getting rid of data_files--it's dangerous.  But package_data I find very useful sometimes, and I don't think it's always wrong.  At the very least, it's not clear to me how the above use case is intended to be replaced.
History
Date User Action Args
2011-04-09 18:09:43erik.braysetrecipients: + erik.bray, tarek, eric.araujo, alexis
2011-04-09 18:09:43erik.braysetmessageid: <1302372583.74.0.876049331605.issue11805@psf.upfronthosting.co.za>
2011-04-09 18:09:37erik.braylinkissue11805 messages
2011-04-09 18:09:37erik.braycreate