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.  
  
— Donald Stufft  

On Apr 27 2016, at 2:05 pm, Daniel Holth <dho...@gmail.com> wrote:  

> I feel differently.

>

> 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?

>

>  

>

> On Wed, Apr 27, 2016, 13:52 Donald Stufft
<[don...@stufft.io](mailto:don...@stufft.io)> wrote:  

>

>> 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.

>>

>>  
  
— Donald Stufft

>>

>>  

>>

>> On Apr 27 2016, at 1:38 pm, Ethan Furman
<[et...@stoneleaf.us](mailto:et...@stoneleaf.us)> wrote:  

>>

>>> On 04/26/2016 07:10 AM, Donald Stufft wrote:

>>>

>>> > Alternatively, he could have just produced a wheel from any checkout
at  
> all if the MANIFEST.in excluded a file that would otherwise have been  
> installed.

>>>

>>> Yes. My MANIFEST.in starts with an 'exclude enum/*' and then includes  
all files it wants.

>>>

>>> > This sort of thing is why I'm an advocate that we should only  
> build sdists from checkouts, and wheels from sdists (at the low level  
> anyways, even if the UI allows people to appear to create a wheel  
> straight from a checkout).

>>>

>>> My current process is:

>>>

>>>    python3.5 setup.py sdist --format=gztar,zip bdist_wheel upload

>>>

>>> What should I be doing instead?

>>>

>>> \--  
~Ethan~

>>>

>>> _______________________________________________  
Distutils-SIG maillist - [Distutils-SIG@python.org](mailto:Distutils-
s...@python.org)  
<https://mail.python.org/mailman/listinfo/distutils-sig>

>>

>> _______________________________________________  
Distutils-SIG maillist  -  [Distutils-SIG@python.org](mailto:Distutils-
s...@python.org)  
<https://mail.python.org/mailman/listinfo/distutils-sig>  

_______________________________________________
Distutils-SIG maillist  -  Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig

Reply via email to