-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Enforce mypy compliance in CI #3197
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
mypy failures now make CI fail: https://dev.azure.com/xarray/xarray/_build/results?buildId=511&view=logs Now moving to solve them... |
coords: Mapping[Hashable, Any] = None, | ||
attrs: Mapping = None, | ||
attrs: Mapping[Hashable, Any] = None, |
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.
Support Dataset({"x": [1, 2]})
, where one of the data_vars is silently moved to coords
Ready for review and merge |
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.
+1 from me, though worth waiting if anyone has objections. If this becomes a burden for new contributors, we can easily revert
Is there a pre-commit for mypy? |
Co-Authored-By: Maximilian Roos <[email protected]>
@max-sixty added and tested :) |
Okay, we can give this a try |
In it goes |
* upstream/master: chunk sparse arrays (pydata#3202) Annotations for .data_vars() and .coords() (pydata#3207) Remove duck_array_ops.as_like_arrays() (pydata#3204) Match mypy version between CI and pre-commit hook (pydata#3203) BUG fix +test .sel method gives error with float32 values (pydata#3153) fix precommit file (pydata#3201) Enforce mypy compliance in CI (pydata#3197)
No description provided.