-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Run against all of Python standard library modules and report issues #636
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
Comments
I think that we should do this in the near future, maybe as part of a more general project to fix false positives. |
I went ahead and did this on my flight home. I'll start filing issues later, but my raw notes are here: https://gist.github.com/ethanhs/ccab320935ba8705949472190d77a4b7 |
Okay I filed issues for everything there doesn't already seem to be an issue for. Let me know if there are further questions/concerns. |
Since individual issues are opened now, should we close this one? |
@ethanhs this is great! Are you also going to report the typeshed issues you found? |
Closing as I've opened issues for the bugs in mypy and python/typeshed#2149 for typeshed. |
@ethanhs Thank you for doing this! Fixing bogus errors generated from unannotated code is important, since this is the first thing many users experience when trying out mypy, and we want the first impression to be a good one :-) |
Uh oh!
There was an error while loading. Please reload this page.
Run mypy against all Python 3.7 standard library modules (that are implemented in Python and have no missing C extension dependencies) and file bogus errors that mypy reports as bugs.
The text was updated successfully, but these errors were encountered: