This repository has been archived by the owner on Jul 5, 2023. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 54
mypy --fast-parser option broken with 1.0.0 #31
Comments
mypy has moved to the |
It's expected that mypy 0.47* doesn't work with typed-ast 1.0+.
…--Guido (mobile)
On Feb 16, 2017 12:21 PM, "Ethan" ***@***.***> wrote:
mypy has moved to the mypy package name, and is at version 0.471, if you
update mypy to 0.471, does that fix the issue?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#31 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACwrMu4eKa7xiYmAOTMoqH3PrEbpH7SBks5rdK_kgaJpZM4MDfQe>
.
|
This is expected -- typed_ast made some backwards incompatible changes when updating to 1.0. To fix, use mypy (no longer mypy-lang) version 0.471, which has an upper bound on the typed-ast version it installs. The next release of mypy will be out in a couple weeks and will be updated to work with typed-ast 1.0. |
Resolved with the mypy package for me. Thanks all. Leaving a link here to the blog post explaining the changes for anyone else coming across this: http://mypy-lang.blogspot.com/2017/01/mypy-0470-released.html |
tbbharaj
pushed a commit
to tbbharaj/typed_ast
that referenced
this issue
Dec 6, 2021
Allow bytearray arguments, and return bytearrays for block functions on Python 3
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Running in a Python 3.6.0 virtual environment, running mypy with --fast-parser option does not work with typed-ast==1.0.0:
The same run works with typed-ast==0.6.3
The text was updated successfully, but these errors were encountered: