What is the naming convention used for the Python wheels at Christoph Gohlke's Unofficial Windows Binaries for Python Extension Packages?
For example, for scipy here are two of names of wheels on the page:
scipy-0.17.0-cp27-none-win32.whl
scipy-0.17.0-cp27-none-win_amd64.whl
What does 'none' indicate?
What's the difference between win32 and win_amd64?
Does it matter if I'm using the x86 or x86-64 version of Python (ref Python 2.7.11)?
It may harm your system.
pip installs from PyPI. pipwin installs from Christoph Gohlke's Unofficial Windows Binaries for Python Extension Packages. Quite often there are more and better compiled wheels at the Christoph's Unofficial site. Compare, for example, PyAudio (one of the most problematic packages, see how many question there are).
pipwin is a complementary tool for pip on Windows. pipwin installs unofficial python package binaries for windows provided by Christoph Gohlke here http://www.lfd.uci.edu/~gohlke/pythonlibs/ Version 0.2. X changes the structure of cache file. Make sure to run `pipwin refresh` if updated.
Actually that's the wheel tool "naming convention". Sincerely I'm not sure what "none" indicates, but yes, your Python version matters. If you're using the 32-bit interpreter, then go ahead with the win32
option (under Windows, of course). Otherwise download the win_amd64
version for 64-bit distributions.
Hope it helps!
tl;dr: it's the wheel naming convention and none
means it's pure python.
I've taken the extra step to follow answer/comments.
The none
in this case is probably the ABI tag. From PEP 425:
The ABI tag indicates which Python ABI is required by any included extension modules. For implementation-specific ABIs, the implementation is abbreviated in the same way as the Python Tag, e.g. cp33d would be the CPython 3.3 ABI with debugging.
So none
in this case means the package is advertised as "pure-python" (none of it's local dependencies require a specific application binary interface).
This is assuming the provided wheel files are names using the official wheel file name convention:
The wheel filename is {distribution}-{version}(-{build tag})?-{python tag}-{abi tag}-{platform tag}.whl.
distribution
Distribution name, e.g. 'django', 'pyramid'.
version
Distribution version, e.g. 1.0.
build tag
Optional build number. Must start with a digit. A tie breaker if two wheels have the same version. Sort as the empty string if unspecified, else sort the initial digits as a number, and the remainder lexicographically.
language implementation and version tag
E.g. 'py27', 'py2', 'py3'.
abi tag
E.g. 'cp33m', 'abi3', 'none'.
platform tag
E.g. 'linux_x86_64', 'any'.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With