问题
To my knowledge, the naming rules of python wheel is
package_version-related_python_version-none-32bits_or_64bits.whl
For example,
numpy‑1.11.2+mkl‑cp35‑none‑win_amd64.whl
is numpy of version 1.11.2 for Python3.5 running in windows 64 bits platform. Reference
Currently i have noticed the naming of Python packages in Unofficial Windows Binaries for Python Extension Packages use 'cpxxm' to replace 'none'. For example,
numpy‑1.11.2+mkl‑cp35‑cp35m‑win_amd64.whl
When installing these packages, pip will return version unmatch error. When i change 'cp35m' to 'none', it becomes normal.
So, what is the meaning of 'cp2xm' 'cp3xm' and why suddenly all the package replace 'none' with 'cpxxm'?
回答1:
From PEP 3149 the m indicates pymalloc is in use as the memory allocator
The second component of the wheel name is the "abi" component. This was always none in wheels produced by older versions of wheel <26 as abi detection wasn't yet implemented.
In newer versions of wheel, the abi is populated. You need a sufficiently new version of pip in order to install these wheels.
来源：https://stackoverflow.com/questions/40625611/what-is-the-meaning-of-cp3xm-and-cp2xm-in-the-name-of-python-wheels