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

Continue analysis after parse errors #969

Closed
JukkaL opened this issue Nov 2, 2015 · 2 comments
Closed

Continue analysis after parse errors #969

JukkaL opened this issue Nov 2, 2015 · 2 comments

Comments

@JukkaL
Copy link
Collaborator

JukkaL commented Nov 2, 2015

As continuation of #966, mypy should continue processing additional modules even if there is a parse error in one module. Currently mypy stops at a parse error.

Any module that can't be parsed should be considered to be the equivalent of having type Any elsewhere in the program.

@JukkaL
Copy link
Collaborator Author

JukkaL commented Nov 22, 2015

As the parser is now in better shape this is no longer as urgent as this used to be.

@hauntsaninja
Copy link
Collaborator

While blocking errors are a bad experience, they're fairly rare these days

@hauntsaninja hauntsaninja closed this as not planned Won't fix, can't repro, duplicate, stale Aug 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants