Hi Philip<br><br><div><span class="gmail_quote">On 1/15/07, <b class="gmail_sendername">Phillip J. Eby</b> <<a href="mailto:pje@telecommunity.com">pje@telecommunity.com</a>> wrote:</span><blockquote class="gmail_quote" style="margin-top: 0; margin-right: 0; margin-bottom: 0; margin-left: 0; margin-left: 0.80ex; border-left-color: #cccccc; border-left-width: 1px; border-left-style: solid; padding-left: 1ex">
At 02:16 PM 1/15/2007 +0100, Arve Knudsen wrote:<br>>Hi<br>>I'm experiencing a problem when using setuptools (0.6c5) to generate a<br>>source tarball, using the 'sdist' command. What happens is that data files
<br>>(PNGs) are omitted even though I include them in package_data (keyword to<br>>setup), and they are correctly included when installing. Is it the<br>>intended behaviour of 'sdist' to ignore package_data, or is this a bug?
<br><br>They should be included in the sdist. Are you using CVS or Subversion, and<br>if so, are the .png files under revision control? That information will<br>help me narrow down what the problem is.<br></blockquote></div>
<br>After having sent this mail, I did some more digging on Google and from what I understand sdist doesn't actually support the 'package_data' keyword, right? This should really be better pointed out in the documentation, as some of my colleagues also struggled with this before.
<br><br>So I tried 'include_package_data' instead, after having extended setuptools with support for the Mercurial VCS. This made sdist include also each and every version-controlled Python file however. Is this the intended behaviour? So in the end I resorted to
MANIFEST.in, although I'd prefer to keep this within setup.py.<br><br>If there's any interest I can provide the source for my Mercurial extension (simple as it may be).<br><br>Thanks,<br>Arve Knudsen<br>