Oops, On Tue, Sep 23, 2014 at 1:50 PM, Matthew Brett <matthew.br...@gmail.com> wrote: > Hi, > > On Mon, Sep 22, 2014 at 10:46 AM, Charlie Clark > <charlie.cl...@clark-consulting.eu> wrote: >> Am .09.2014, 16:42 Uhr, schrieb Matthew Brett <matthew.br...@gmail.com>: >> >>> So just to be clear, the difference here is between the instlal you got >>> for: >>> pip install your-package >> >> >>> where `your-package` was either an sdist built with ``python setup.py >>> sdist`` or a wheel built with ``python setup.py bdist_wheel``? >> >> >>> Is your package online somewhere to have a look at the setup.py? >> >> >> https://bitbucket.org/openpyxl/openpyxl/src >> >>> My best guess would be you had some custom code for building the sdist >>> that is not being run for other distutils build commands. If that's >>> the case, then you could certainly reasonably blame the fact that >>> distutils is complicated, but it would not be a general problem with >>> wheels. >> >> >> No, as I said the manifest wasn't being respected with wheels so we stopped >> using them. No idea whether this applies to any other projects or why it is. >> As I said before, Python's packaging is still a work in progress. > > The MANIFEST only specifies the files to put into the sdist, so this is > the documented behavior (though maybe what you'd expect).
Sorry - obviously - "maybe _not_ what you'd expect" - it certainly wasn't what I expected. Having said that, these are - er - features of distutils, and wheels just give the same as ``python setup.py install`` - as do other binary installer options, which seems reasonable to me. Cheers, Matthew _______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org https://mail.python.org/mailman/listinfo/pythonmac-sig unsubscribe: https://mail.python.org/mailman/options/Pythonmac-SIG
