-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Make typed_ast mypy's default and only parser #1353
Comments
After this is complete, we can start converting mypy to use typed_ast's ast (which is very similar to the official python ast) node by node (which will further help perf). |
|
@ddfisher: I've created a label "New Parser" and added it to all issues that look like they would be fixed by the new parser or could be fixed once the new parser is the only parser. |
The progress of making typed_ast compile and run on Windows is being tracked in this issue: python/typed_ast#20 |
Since typed_ast now supports Windows fully, would there be interest in me working on appveyor integration? I know it was tried previously, but once this is completed, I see no reason why it shouldn't be added. |
Yes @ethanhs we would it if you could contribute Appveyor integration! I once tried but didn't understand how it was supposed to work. |
Currently, typed_ast is mypy's preferred parser (as it's much faster, more correct, and supports features like multiline type comments), but it is not yet mypy's default parser. The main blocker to this is Windows support.
Here are the high-level items remaining:
The text was updated successfully, but these errors were encountered: