Skip to content

Cannot add grpcio #328

@a-musing-moose

Description

@a-musing-moose
  • 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).
  • OS version and name: Ubuntu 18.04
  • Poetry version: 0.11.2
  • Python version: 3.6.5

Issue

When trying to add grpcio using poetry add grpcio I expect it it install grpcio. Instead I get a resolver error:

Using version ^1.13 for grpcio

Updating dependencies
Resolving dependencies... (0.2s)
                                                                                                       
[SolverProblemError]                                                                    
The current supported Python versions are 3.6.5                                                      
Because no versions of grpcio match >1.13,<2.0                                                       
 and grpcio (1.13.0) depends on futures (>=2.2.0), grpcio (>=1.13,<2.0) requires futures (>=2.2.0).  
Because futures (3.2.0) requires Python >=2.6, <3                                                    
 and no versions of futures match >=2.2.0,<3.2.0 || >3.2.0, futures is forbidden.                    
Thus, grpcio is forbidden.                                                                           
So, because whodat depends on grpcio (^1.13), version solving failed.                                
                                                                                                       
add [-D|--dev] [--git GIT] [--path PATH] [-E|--extras EXTRAS] [--optional] [--python PYTHON] [--platform PLATFORM] [--allow-prereleases] [--dry-run] [--] <name> (<name>)...

Looking at the setup.py for grpcio the only reference to the failed dependency futures is inside a if not PY3 block (https://github.com/grpc/grpc/blob/v1.13.0/setup.py#L281), so should not actually form part of the requirements as far as I can see.

I'm not sure why the resolving is still seeing the futures dependency.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions