Cannot install CPython 3.10 wheels

[Gelbpunkt]

Environment

• pip version: 20.1.1
• Python version: 3.10a0
• OS: Alpine Linux Edge (3.12rc1)

Running inside a container

Description
Whenever I build a wheel with pip wheel . for a package like Cython, I get an error when installing it, saying the wheel is unsupported. However, py3-none-any-wheels install and build fine.

Expected behavior
I expected it to install, just like in 3.9.

How to Reproduce
Compile CPython 3.10a0 from GitHub, clone Cython, build the wheel, install it.

Output

$ pip wheel .
Processing /build/cython
Building wheels for collected packages: Cython
  Building wheel for Cython (setup.py): started
  Building wheel for Cython (setup.py): still running...
  Building wheel for Cython (setup.py): finished with status 'done'
  Created wheel for Cython: filename=Cython-3.0a5-cp310-cp310-linux_x86_64.whl size=5974718 sha256=6d80fb47595bf2090a07ad3836e74ce1391622d34a8166b063adbd557a3ebf40
  Stored in directory: /tmp/pip-ephem-wheel-cache-isxd6eex/wheels/cb/cf/fc/8e1fbc2f1194a1ecc534d6a5475f16b988e7f7ddf7d944bffe
Successfully built Cython
$ pip install Cython-3.0a5-cp310-cp310-linux_x86_64.whl
ERROR: Cython-3.0a5-cp310-cp310-linux_x86_64.whl is not a supported wheel on this platform.

Further Debug Info

>>> from pip._internal.models.target_python import TargetPython
>>> TargetPython().get_tags()
[<cp3_10-cp3_10-linux_x86_64 @ 140573016538560>, <cp3_10-abi3-linux_x86_64 @ 140573015248832>, <cp3_10-none-linux_x86_64 @ 140573018235392>, <cp39-abi3-linux_x86_64 @ 140573016111168>, <cp38-abi3-linux_x86_64 @ 140573016110784>, <cp37-abi3-linux_x86_64 @ 140573015672896>, <cp36-abi3-linux_x86_64 @ 140573017887232>, <cp35-abi3-linux_x86_64 @ 140573017788480>, <cp34-abi3-linux_x86_64 @ 140573016476096>, <cp33-abi3-linux_x86_64 @ 140573016476736>, <cp32-abi3-linux_x86_64 @ 140573016398080>, <py3_10-none-linux_x86_64 @ 140573024218560>, <py3-none-linux_x86_64 @ 140573016538624>, <py39-none-linux_x86_64 @ 140573023969472>, <py38-none-linux_x86_64 @ 140573016446976>, <py37-none-linux_x86_64 @ 140573014209408>, <py36-none-linux_x86_64 @ 140573016105216>, <py35-none-linux_x86_64 @ 140573016108800>, <py34-none-linux_x86_64 @ 140573016108352>, <py33-none-linux_x86_64 @ 140573016817216>, <py32-none-linux_x86_64 @ 140573016816512>, <py31-none-linux_x86_64 @ 140573016815936>, <py30-none-linux_x86_64 @ 140573016815424>, <cp310-none-any @ 140573016814528>, <py3_10-none-any @ 140573016814912>, <py3-none-any @ 140573016817344>, <py39-none-any @ 140573016776832>, <py38-none-any @ 140573016777344>, <py37-none-any @ 140573016777600>, <py36-none-any @ 140573016778112>, <py35-none-any @ 140573016778496>, <py34-none-any @ 140573016778752>, <py33-none-any @ 140573016779328>, <py32-none-any @ 140573016780160>, <py31-none-any @ 140573016674496>, <py30-none-any @ 140573016675072>]

[uranusjr]

Looks like a setuptools bug to me. The 3.10 tag should use 3_10 (see pypa/packaging#240), so TargetPython is doing the right thing (it ultimately calls into packaging.tags). It’s the setup.py wheel command that’s generating the wrong file name, and that’s controlled by setuptools, not pip.

Edit: Or more likely, a bug in wheel; which actually builds the wheel.

Edit 2: Confirmed this is a wheel bug, reported as pypa/wheel#354.

[ichard26]

pypa/wheel#354 has been resolved for a long time, this issue isn't relevant anymore.