Disable installation of Windows-specific files on non-Windows systems #1
setuptools/cli-arm-32.exe : PE32 executable (console) Unknown processor type 0x1c4, for MS Windows
For more info see (ADD-ON INFO button):
The text was updated successfully, but these errors were encountered:
Those files are windows launchers for the launching scripts on Windows systems. The executables must be present in the package in order for Windows users to be able to reliably launch scripts.
Eventually, these launchers should be replaced by PEP 397 launchers, but for now, they're a necessary part of the source distribution.
I agree with presence of *.exe files in tarballs, but I think that setup.py could skip installation of *.exe files on non-Windows systems. (MANIFEST.in already includes these files.)
I have some concerns about the patch as applied. The patch adds additional dependency on MANIFEST.in (as you indicated). However, this new reliance renders fragile another objective (distribute #372). We would like to eliminate the (redundant) reliance on MANIFEST.in and rely instead only on packaging metadata as supplied setup.py. With this patch and with MANIFEST.in removed, however, if one builds the sdist on anything but Windows, it will be missing the files in the sdist.
In my mind, having a cleaner declaration of package parameters (in one file, setup.py) is of greater value than of not having Windows executables installed on Unix operating systems, as the former can cause packaging errors, while the latter is only an annoyance.
This seems to be broken again, at least with
It works for me. Using a source checkout of both Setuptools 2.2 and the latest tip on Ubuntu 14.04:
That is, no executables are found.
Is it possible that SETUPTOOLS_INSTALL_WINDOWS_SPECIFIC_FILES is set on your host (or by pip)?
Since I can't replicate the behavior on a Linux box, I must conclude the problem is resolved, but do please feel free to delve into the problem further and provide more detail about what might be going wrong.