Fix some of the warnings triggered by numpy 1.19 #2239
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report
@@ Coverage Diff @@
## master #2239 +/- ##
=======================================
Coverage 71.85% 71.85%
=======================================
Files 154 154
Lines 20647 20655 +8
=======================================
+ Hits 14835 14841 +6
- Misses 5812 5814 +2 |
astafan8
approved these changes
Oct 5, 2020
jenshnielsen
force-pushed
the
numpy_119_fix_dtype_warnings
branch
from
5cdea8e
to
1b1b9c3
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Only use instantiable types as dtypes when creating arrays. Using the non concrete types triggers a warning and will be an error in the future