"filename.whl is not a supported wheel on this platform"

Question

I saw the same question, but it didn't work for me.

pip install PyOpenGL.3.1.1-cp34-cp34m-win_amd64.whl

I also have the same problem for NumPy:

pip install numpy-1.11.1+mkl-cp34-cp34m-win_amd64.whl

Then I get:

numpy-1.11.1+mkl-cp34-cp34m-win_amd64.whl is not a supported wheel on this platform. Storing debug log for failure in C://Users/myUsername/pip/pip.log

I'm using 64-bit and Python 3.4.0. What is wrong?

Solution 1

Try updating pip first before you rename pip install --upgrade pip

Solution 2

You'll probably have to rename your .whl file like numpy-1.11.1+mkl-cp34-none-win_amd64.whl before installing. Your pip has a finite number of tags it recognizes in wheel filenames.

See this answer for more on this: Cannot install numpy from wheel format

Solution 3

1. Check the supported tags for wheel version for your system(platform).
2. To check supported tag run the following command pip debug --verbose
3. When you run the command, you will get many lists, along with supported tags, download compatible wheel file from supported tags.
4. install wheel file using this command pip install pycurl-7.43.0.4-cp37-cp37m-win_amd64.whl

Supported tags portion looks like:

Solution 4

There are several things to consider

Python versions should match, OS should be 64 bit and python should also be 64 bit.

And as in your case both of these conditions are met, you have to make sure that pip is able to handle all the fields in wheel file name.

For example in my case my pip was not handling "cp35m"

To ensure, in python shell

import pip

Then type

pip.pep425tags.get_supported()

you should be able to see all the fields your pip command can handle. If any one is missing try updating Pip first.

However in my case even updating was giving error. So I uninstalled python 3.5.1 and installed python 3.5.2, and that worked for me.

Solution 5

Things to check for:

1. Even though I my system is 64 I had 32 python installed. You can check this by opening your IDLE.
2. I had python 2 and 3 installed so updating pip was updating the wrong python for me. And of course I just wasn't trying to install the right kind of package because it was the wrong python version in the path.
3. If you are still having some problems like me where doing pip2 or pip3 fixes didn't seem to work, I did a quick fix. My pip only had python 3 in its path, so I went to systems>advanced system settings>environment variables and then added "C:\Python27\Scripts\" to the PATH variable. This solved my issues.

View more solutions

Comments

[konoufo]

Same thing applies for Pyopengl and all wheel packages.

[PixelArtDragon]

I'm having the same problem only with Python 2.7, and renaming is not working.

[konoufo]

How did you rename it ? What's the new name you set ?

[PixelArtDragon]

I renamed it with the same formula, with none instead of the second cp27 tag.

[konoufo]

you should really open a python shell and check the output of : import pip; print pip.pep425tags.get_supported() (Copy-paste the result here). Moreover, is your python installation a 64-bit installation ?

[Roeland]

Starting with Python 3.8 and pip 19.2.3 on Windows there is no "m" at the end of the second cp38 tag. The correct wheel name is numpy-1.17.1+mkl-cp38-cp38-win_amd64.whl. See here and here.

[Roeland]

Starting with pip 10 and later, pip.pep425tags has been moved to pip._internal.pep425tags. See here.

[user2030113]

I have tried like this it worked for me too!! C:\Users\Python\Python34\Scripts>pip install C:\Users\Downloads\Cython-0.28-cp34-cp34m-win_amd64.whl Cython-0.28-cp34-cp34m-win_amd64.whl is not a supported wheel on this platform. C:\Users\Python\Python34\Scripts>pip install C:\Users\Downloads\Cython-0.28-cp34-none-win_amd64.whl Processing c:\users\downloads\cython-0.28-cp34-none-win_amd64.whl Installing collected packages: Cython Successfully installed Cython-0.28

[Peter Mortensen]

Re "interrupter": Do you mean "interpreter"? (Python interpreter)

[Soroosh Bateni]

Thanks! This solved the issue for me.

[404pio]

In my case it is not working. Can you elaborate why it should help?

[DSchmidt]

Because pip needs to update to learn new versions. It doesn't automatically know what your python version is capable of.