Repository navigation
mypy 0.471 not finding typed-ast 1.0.0 when using --fast-parser #2862
Description
python3 -c "from typed_ast import ast27, ast3" doesn't raise an ImportError and yet running mypy keeps telling me:
You must install the typed_ast package before you can run mypy with `--fast-parser`.
You can do this with `python3 -m pip install typed-ast`.
It looks like mypy 0.471 imports typed_ast.ast35 which doesn't exist in typed_ast 1.0.0.
Activity
gvanrossum commentedon Feb 14, 2017
I had this problem too, reinstalling (
pip3 install -U) didn't help. But it went away after I manually removed site-packages/mypy/ and then reinstalled again.gvanrossum commentedon Feb 14, 2017
Hm, I wonder if some metadata lingers around when you use
pip uninstalland doesn't get overwritten when you reinstall?ilevkivskyi commentedon Feb 14, 2017
It looks like this happened to me, typeshed was not overwritten, until I completely removed it manually.
brettcannon commentedon Feb 14, 2017
Apparently explicitly installing typed-ast first solved the issue as well: python/the-knights-who-say-ni#93.
samuelcolvin commentedon Feb 17, 2017
This seems to still be a problem, even with release of typed-ast-1.0.1, see this travis build for example.
Locally I've tried completely deleting my virtualenv directory and recreating but to no avail.
gvanrossum commentedon Feb 17, 2017
@samuelcolvin You're still using mypy 0.4.6. You gotta update your test/requirements.txt to use
mypy==0.471instead ofmypy-lang=0.4.6. (Note the different spelling of both the package name and the version.)samuelcolvin commentedon Feb 17, 2017
Thanks, I also had to remove the
typed-astrequirement to allow mypy to install the version oftyped-astit wants.As per this mypy 4.7 requires
typed-ast >= 0.6.3, < 0.7.0and (for me at least) alwasy fails with 1 or 1.0.1gvanrossum commentedon Feb 17, 2017
emmatyping commentedon Sep 6, 2017
I believe this can be closed. If someone encounters an issue with a newer release, please open a new issue.