<head></head><body>You can try to patch around the problem (and do it in every single alternative build system once we enable support for that) or you can just fix the problem at the "protocol" level once and for all. The fundamental problem isn't with MANIFEST.in, it's that some indeterminite steps need to run to produce a sdist and unless you make sure you run every single one of those steps you can have no confidence that the results of producing a wheel from a VCS checkout will be the same as installing from a sdist or building a wheel from a sdist.<br><br><!-- <signature> -->— Donald Stufft<br><!-- </signature> --><div class="gmail_quote">
On Apr 27 2016, at 2:05 pm, Daniel Holth <dholth@gmail.com> wrote:
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div dir="ltr">I feel differently.</div><span>
</span><p dir="ltr">Bdist_wheel just doesn't understand MANIFEST.in . Perhaps support could be adapted from bdist_egg or other bdist implementations. Wheel doesn't do everything the setuptools or distutils implementations put into their dist commands. Even something as simple as a forced clean of the dist directory on init may fix the problem?</p><span>
</span><br><div><div dir="ltr">On Wed, Apr 27, 2016, 13:52 Donald Stufft <<a href="mailto:donald@stufft.io" target="_blank">donald@stufft.io</a>> wrote:<br></div><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>This isn't really a problem with what you're doing. Rather it's an issue with the toolchain and and open question whether or not wheels should conceptually be able to be produced from a checkout, or if they should only be produced from a sdist. Problems like this are why I advocate the Checkout -> sdist -> wheel being the only path, but others feel differently.</div><div><br><br>— Donald Stufft</div><div><br><div>
On Apr 27 2016, at 1:38 pm, Ethan Furman <<a href="mailto:ethan@stoneleaf.us" target="_blank">ethan@stoneleaf.us</a>> wrote:
<br>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<p>On 04/26/2016 07:10 AM, Donald Stufft wrote:</p>
<p>> Alternatively, he could have just produced a wheel from any checkout at<br>> all if the MANIFEST.in excluded a file that would otherwise have been<br>> installed.</p>
<p>Yes. My MANIFEST.in starts with an 'exclude enum/*' and then includes <br>all files it wants.</p>
<p>> This sort of thing is why I'm an advocate that we should only<br>> build sdists from checkouts, and wheels from sdists (at the low level<br>> anyways, even if the UI allows people to appear to create a wheel<br>> straight from a checkout).</p>
<p>My current process is:</p>
<p> python3.5 setup.py sdist --format=gztar,zip bdist_wheel upload</p>
<p>What should I be doing instead?</p>
<p>--<br>~Ethan~</p>
<p>_______________________________________________<br>Distutils-SIG maillist - <a href="mailto:Distutils-SIG@python.org" target="_blank">Distutils-SIG@python.org</a><br><a href="https://mail.python.org/mailman/listinfo/distutils-sig" target="_blank">https://mail.python.org/mailman/listinfo/distutils-sig</a></p>
</blockquote>
</div></div>_______________________________________________<br>
Distutils-SIG maillist - <a href="mailto:Distutils-SIG@python.org" target="_blank">Distutils-SIG@python.org</a><br>
<a href="https://mail.python.org/mailman/listinfo/distutils-sig" rel="noreferrer" target="_blank">https://mail.python.org/mailman/listinfo/distutils-sig</a><br>
</blockquote></div>
</blockquote>
</div></body>