... is not a supported wheel on this platform

Hey.

I have a wheel issue as I have seen a couple of others have but after going through all the different threads I can't seem to get a solution going. Quick info:

I run windows 10 and have created a virtual env via conda. My env specs are:

Python 3.6.9
Pip v. 19.3.1

When I go print(wheel.pep425tags.get_supported())

I get:

[('cp36', 'cp36m', 'win_amd64'), ('cp36', 'none', 'win_amd64'), ('cp36', 'none', 'any'), ('cp3', 'none', 'any'), ('cp35', 'none', 'any'), ('cp34', 'none', 'any'), ('cp33', 'none', 'any'), ('cp32', 'none', 'any'), ('cp31', 'none', 'any'), ('cp30', 'none', 'any'), ('py3', 'none', 'win_amd64'), ('py36', 'none', 'any'), ('py3', 'none', 'any'), ('py35', 'none', 'any'), ('py34', 'none', 'any'), ('py33', 'none', 'any'), ('py32', 'none', 'any'), ('py31', 'none', 'any'), ('py30', 'none', 'any')]

My file is located at (and is named) "C:\Users\Admin\Desktop\prodigy-1.9.5-cp36.cp37.cp38-cp36m.cp37m.cp38-win_amd64.whl"

I have run the following command in bot pip and pip3 (and also tried adding and removing m at the last cp38):

pip install prodigy-1.9.5-cp36.cp37.cp38-cp36m.cp37m.cp38-win_amd64.whl

It still says: "is not a supported wheel on this platform."

Any advice?

Hi! What happens if you rename the file from ...cp38-win_amd64.whl to ...cp38m-win_amd64.whl? It's a wild guess, but there has been an issue with the setuptools appending/not appending the m flag (see here), which means we had to rename all wheels we ship for our packages. But depending on the version of pip, maybe it does care about the m being there in your case.

It says the same thing. Oddly, by mistake, I pip'ed it into my base env and that worked but it still doesn't work on the env I dedicated to it. Are there any dependencies I need to make sure exists first? I haven't gone through the list but I have all sorts of weird stuff in my base env.

That's very strange – but also kinda good news :slightly_smiling_face: The dependencies shouldn't make a difference (and the wheel should install everything it needs). The error you're seeing means that pip doesn't even acknowledge the file as valid, so you're not even getting to the install stage.

Which pip versions are you running in both envs? And if they're different, maybe try installing the same pip version your base env has in your new env? It could easily be some pip version weirdness.

You were right on the money - different versions of pip. Thank you for your help and a really amazing tool. I can't wait to play around with it!

1 Like

@rolflund Glad you got it working! Just curious, which versions of pip were you using, and which one worked? Just so I know in case this (or a similar problem) comes up again in the future :slightly_smiling_face:

Hi, I also get the same error. I'm using ubuntu OS with pip version 19.0.3. May I know which version required, please.

The version shouldn't matter – just make sure the wheel is named correctly and matches your platform, because that's what pip cares about. Also make sure that the local path is correct (and try pip install *.whl so you don't have to repeat the file name on the command line).