-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
check mypy at the end of some CI runs? #4881
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
Comments
that's true, |
Works for me. I am also fine only testing in the xarray/xarray/core/npcompat.py Lines 82 to 85 in 0b8ec0c
|
We currently run mypy in the
pre-commit hooks
CI. However, this is done in an environment where no dependencies are installed. Therefore we missed the errors that pop up when running mypy with numpy 1.20 installed. (Please correct my if I misunderstood this). Should we add a new step to our CI and run mypy?I think we should at least add this to
ubuntu-latest py3.8
. For more complete checks we could also go forubuntu-latest py37-min-all-deps
andupstream-dev
.The text was updated successfully, but these errors were encountered: