-
Notifications
You must be signed in to change notification settings - Fork 129
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
Improve typing experience with CI #1516
Comments
Well right now we haven't configured Pyright to check types at all: Line 16 in f9a071f
Even if/when we enable that option, is one strictly a subset of the other? Based on Pyright's comparison, it looks like each has its pros and cons. |
i guess i don't see what this is improving. if the mypy test fails during CI for a particular python version, doesn't that indicate potential runtime issues with that particular python version? isn't surfacing that during CI beneficial? |
Apologies, the reasoning should have been in the issue description. This is what I think happened with @jameshadfield yesterday in #1506:
Had he clicked a Python 3.8 job the first time around, he would have seen all the errors to fix:
but that's not very obvious from the GitHub UI since all Python 3.8 jobs were marked "canceled". We really only care about mypy errors from the Python 3.8 job, so those should the only ones reported. |
Discussion on Slack.
The text was updated successfully, but these errors were encountered: