[Distutils] Wheels and dependent third party dlls on windows

Daniel Holth dholth at gmail.com
Wed Oct 1 22:06:26 CEST 2014

On Wed, Oct 1, 2014 at 1:35 PM, Paul Moore <p.f.moore at gmail.com> wrote:
> On 1 October 2014 17:44, David Genest <david.genest at ubisoft.com> wrote:
>> - If you run python setup.py bdist_wheel, the dlls specified in the scripts parameter end up in the wheel archive and does what is needed for our setup. (the dlls are copied to the scripts directory which is on PATH for the activated environment).
> It sounds like you're using an old version of wheel. The
> --skip-scripts argument was removed (and skipping scripts made the
> default) in 0.23.0.
>> - On the other hand, if you run pip wheel on the same package, the dlls are not placed in the archive. Is this a pip bug ?
> No, this is not a pip bug. Scripts are omitted from wheels and
> generated on install from the metadata. DLLs aren't scripts, and
> putting them into the scripts list in setup.py will cause them to be
> treated inappropriately (as you see).

You are confusing generated entry_points script wrappers with the
setup(scripts=...) scripts. The scripts=... scripts should never be
skipped, even with --skip-scripts, they should work the same as they
always have.

More information about the Distutils-SIG mailing list