-
-
Notifications
You must be signed in to change notification settings - Fork 331
Update dtype usage in zarr/meta.py #700
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
Changes in numpy have led to failures on `mypy zarr/` across a large number of PRs.
Failures can be seen in https://github.com/zarr-developers/zarr-python/pull/699/checks?check_run_id=1904975788
|
Hmm, the |
Do you know what changed? This has nothing to do with the dtype NEPs, but |
Thanks, both. I was assuming it was a numpy bump that led to this, but I'll need to try to find what the change was, unless @Carreau knows. Another possibility is that mypy has gotten stricter, in which case I could update the annotation rather than the logic. |
I would guess the typing is due to NumPy 1.20 now including typing. The |
Codecov Report
@@ Coverage Diff @@
## master #700 +/- ##
==========================================
+ Coverage 99.45% 99.94% +0.48%
==========================================
Files 28 28
Lines 10262 10263 +1
==========================================
+ Hits 10206 10257 +51
+ Misses 56 6 -50
|
Asked for vetoes in gitter. Since all PRs are currently failing, I'm going to merge and start re-running the builds. If there are any issues with the changes here, I'll be happy to open a follow-up PR. |
Changes in zarr's annotations, numpy, and/or mypy have led to failures on
mypy zarr/
across a large number of PRs. This tries to take the most direct route to passing GitHub actions so that PRs can be unblocked.Thanks to @rgommers and @seberg for jumping in.
TODO: