Feb-28-2019, 11:47 AM
with python 3.6.7 and Pipenv:
having astroid and mypy in your Pipfile
you'll get a
Some details in regards to why that
astroid==2.2.0 requires lazy-object-proxy, six, typed-ast<1.3.0
mypy==0.670 requires mypy-extensions<0.5.0,>=0.4.0, typed-ast<1.4.0,>=1.3.1
obviously, this cannot be resolved.
I propose that astroid team tries to change the dependency to allow for newer typed-ast soon.
As a temporary solution, you can lock mypy to 0.660 in your Pipfile using:
having astroid and mypy in your Pipfile
you'll get a
Error:pipenv.exceptions.ResolutionFailure
in case you try to lock Pipenv using commandQuote:pipenv -v lock
Some details in regards to why that
Error:pipenv.exceptions.ResolutionFailure
happens can be found by the command pipenv -v lock
a bit longer up in the output:astroid==2.2.0 requires lazy-object-proxy, six, typed-ast<1.3.0
mypy==0.670 requires mypy-extensions<0.5.0,>=0.4.0, typed-ast<1.4.0,>=1.3.1
obviously, this cannot be resolved.
I propose that astroid team tries to change the dependency to allow for newer typed-ast soon.
As a temporary solution, you can lock mypy to 0.660 in your Pipfile using:
mypy = "==0.660"