Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

astroid blocks for updates to mypy #652

astir13 opened this issue Feb 28, 2019 · 2 comments


None yet
3 participants
Copy link

commented Feb 28, 2019

Steps to reproduce

  1. try to create a pipenv with latest astroid and mypy inside
  2. the dependency of astroid to typed-ast <1.3.0 conflicts with mypy dependency >= 1.3.1 (see
  3. the pipenv -v lock command issues an error

Current behavior

error from pipenv -v lock

Expected behavior

would be nice if astroid could reevaluate its dependency to typed-ast to allow other libraries to use more modern typed-ast

python -c "from astroid import __pkginfo__; print(__pkginfo__.version)" 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

Workaround is of course to set mypy to use version 0.660 in the Pipfile.


This comment has been minimized.

Copy link

commented Mar 4, 2019

I was able to work around this by using python3.7; but it would be nice to still be able to use python3.6.


This comment has been minimized.

Copy link

commented Mar 5, 2019

Thanks @astir13 for creating this issue. The restriction for typed_ast<1.3 was removed and it's going to be part of astroid 2.2.4 once this build finishes

@PCManticore PCManticore closed this Mar 5, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.