poetry: [Linux, 1.1.0a3, Python3.6] X is not a supported wheel on this platform.

  • I am on the latest Poetry version.
  • I have searched the issues of this repo and believe that this is not a duplicate.
  • If an exception occurs when executing a command, I executed it again in debug mode (-vvv option).

Problem with installation of grpcio on Python 3.6 with Poetry 1.1.0a3

First of all looks like faster installation in 1.1 will be a great feature, can’t wait to have it on stable πŸ˜ƒ

However when I tried using that feature to speed up our Docker build I encountered a problem with installation of grpcio on python 3.6 (works on 3.8 fine, also works with Poetry 1.0.9 on both Python versions):

Command ['/root/.cache/pypoetry/virtualenvs/poetry-grpcio-issue-o9msT97p-py3.6/bin/python', '-m', 'pip', 'install', '--no-deps', '/root/.cache/pypoetry/artifacts/e4/1a/fb/cc14443ebcdd3b0d5df7ca7fbffdc7d9343564703a67906925174cd179/grpcio-1.30.0-cp36-cp36m-manylinux2010_x86_64.whl'] errored with the following return code 1, and output:
  grpcio-1.30.0-cp36-cp36m-manylinux2010_x86_64.whl is not a supported wheel on this platform.
  You are using pip version 18.1, however version 20.2b1 is available.
  You should consider upgrading via the 'pip install --upgrade pip' command.


  at /usr/local/lib/python3.6/site-packages/poetry/utils/env.py:937 in _run
       933β”‚                 output = subprocess.check_output(
       934β”‚                     cmd, stderr=subprocess.STDOUT, **kwargs
       935β”‚                 )
       936β”‚         except CalledProcessError as e:
    β†’  937β”‚             raise EnvCommandError(e, input=input_)
       938β”‚
       939β”‚         return decode(output)
       940β”‚
       941β”‚     def execute(self, bin, *args, **kwargs):

You can find minimal working example here.

Cheers!

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 20 (1 by maintainers)

Commits related to this issue

Most upvoted comments

I got a similar error:

  EnvCommandError

  Command ['/Users/allen.c/Library/Caches/pypoetry/virtualenvs/app-6aZ328yD-py3.8/bin/pip', 'install', '--no-deps', '-U', '/Users/allen.c/Library/Caches/pypoetry/artifacts/cd/11/54/fd481eec49cddc06876e526483e7ee8675d0910fed2aa7668a9fc88e62/MarkupSafe-2.0.1-cp38-cp38-mac
osx_10_9_x86_64.whl'] errored with the following return code 1, and output:
  ERROR: MarkupSafe-2.0.1-cp38-cp38-macosx_10_9_x86_64.whl is not a supported wheel on this platform.
  WARNING: You are using pip version 20.2.2; however, version 21.1.2 is available.
  You should consider upgrading via the '/Users/allen.c/Library/Caches/pypoetry/virtualenvs/app-6aZ328yD-py3.8/bin/python -m pip install --upgrade pip' command.

That pip version was a warning and I ignored it. However, at the end I fixed the problem by running what it says

/Users/allen.c/Library/Caches/pypoetry/virtualenvs/app-6aZ328yD-py3.8/bin/python -m pip install --upgrade pip

I’ve just had this exact issue installing cryptography==35.0.0 with poetry==1.1.9 and pip==19.3.1. Updating to poetry==1.1.11 and pip==21.2.4 solved it for me.

@dbalabka But there was a warning message from pip:

You are using pip version 9.0.3, however version 20.2.4 is available. You should consider upgrading via the β€˜pip install --upgrade pip’ command.

The default behaviour is for poetry to delegate the creation of virtual environments to virtualenv, and virtualenv takes care of installing recent versions of pip, setuptools, etc.

Not sure how it happened that you had such an old pip in that virtual environment.

cryptography again? There have been quite some reports of failures on the cryptography dependency. Not sure what the root link between those reports is if any, or if it is just a coincidence. In one of the cases, it turned out to be that the pip version used was too old somehow.

@abn I confirmed it works with develop branch (https://github.com/scoiatael/poetry-grpcio-issue/commit/0d3f83de3ebc8f29c210880993e0f12ad23c01fa). Awesome, thanks for quick response and I’m waiting for next pre-release then πŸ˜ƒ

@scoiatael the root cause for this issue is the default pip version used by the 3.6 container for the virtual environments. Can you try the develop branch? This should have a fix for this (#2666).

pip install git+https://github.com/python-poetry/poetry.git@develop