-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Pin mypy version to 1.6.* #5123
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
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #5123 +/- ##
=======================================
Coverage 89.32% 89.32%
=======================================
Files 205 205
Lines 15188 15188
=======================================
Hits 13566 13566
Misses 1622 1622 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
4c4a3df
to
bbd6192
Compare
@HideakiImamura I resolved the conflict and revised the comment a little. Please take anther look. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Motivation
Temporary fix
Checks(integration)
by adding version specification onmypy
Description of the changes
It appears that
mypy v1.7.0
is causing significant regressions when used in 8000 conjunction withpybind11
, upon which mypy's type inference for torch modules depends. This issue is highlighted in python/mypy#16486.This pull request addresses the problem by setting the
mypy
version tov1.6.*
until the associated bugs are resolved, asPytorch
does here.Alternatives
Add
type:ignore
s and wait for thewarn-unused-ignores
option to detect that the bug has been resolved.