Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork3.1k
Fixast warnings for Python3.12#15558
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
This comment has been minimized.
This comment has been minimized.
JelleZijlstra commentedJun 30, 2023
Seems like there's more to be done. We're getting a None here: The mypy-primer hit also likely indicates a bug. It's something with type comments. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
JelleZijlstra commentedJul 3, 2023
We dropped support for 3.7 by now, so this can probably be simplified; at least there's a big merge conflict now. |
for more information, seehttps://pre-commit.ci
According tomypy_primer, this change doesn't affect type check results on a corpus of open source code. ✅ |
Warnings before:#15330 (comment)
Warnings after:
Zero :)