At 12:43 PM 5/22/2009 -0500, Olemis Lang wrote:
On Thu, May 21, 2009 at 3:56 PM, P.J. Eby <[email protected]> wrote:
> At 11:15 AM 5/20/2009 -0500, Olemis Lang wrote:
>>
>> On Wed, May 20, 2009 at 10:09 AM, Jeff Hammel <[email protected]>
>> wrote:
>> >
>> > You have to verbosely include them with package data. IMHO, this is a
>> > setuptools bug. E.g.:
>> >
>> > package_data={ 'geotrac': ['templates/*', 'htdocs/*'] },
>> > include_package_data=True,
>> >
>> > This is probably not quite right :(, but you get the idea.
>>
>> I just tried this and doesnt include files for sdist ... :(
>>
>> Looking forward for further hints : maybe it's just something I'm
>> doing wrong, dont know, but eggs are ok so I'm not sure
>
> If you are not using a revision control system plugin, you will
have to list
> sdist files in MANIFEST.in;
Thanks, I included files in MANIFEST.in now I can distribute source
packages for TracGViz [1]_ & TracPyTppTheme [2]_ so that EGGs can be
built for different Py versions or whatever ...
So this is the way !
PS: BTW , I dont get the idea about specifying things twice (I mean
package_data & MANIFEST.in ;) Is there a «logical» reason for this ? I
mean why sdist doesnt look for the data specified in package_data ? Or
alternately, what is the reason for having MANIFEST.in too ?
That's what distutils does. setuptools improves on it by adding
revision control support. But if you don't use a revision control
plugin or some other sort of file finder, you have to do it the old
distutils way.
_______________________________________________
Distutils-SIG maillist - [email protected]
http://mail.python.org/mailman/listinfo/distutils-sig
