-
-
Notifications
You must be signed in to change notification settings - Fork 3.5k
Upgrade the pinned version of mypy #8425
Copy link
Copy link
Closed
Labels
area: mypyarea: testingarea: toolinghas prpriority: significantIssues with higher than average priority that do not need to be in the current milestone.Issues with higher than average priority that do not need to be in the current milestone.
Milestone
Metadata
Metadata
Assignees
Labels
area: mypyarea: testingarea: toolinghas prpriority: significantIssues with higher than average priority that do not need to be in the current milestone.Issues with higher than average priority that do not need to be in the current milestone.
I tried doing this as part of #8134 and hit ~400 new errors when checking our code with mypy.
This can be reduced to ~125 errors (many of which are repeated errors about the same code), by disabling mypy's strict optional checking. This check became enabled by default since we last upgraded
mypy. I think we probably should consider enabling this check, but I would recommend disabling it while working on this issue and creating a separate issue to track maybe enabling it and fixing those errors.