Stop using numpy type aliases that were deprecated in 1.20 and later removed #81
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.
The types
np.object
andnp.int
were just aliases for the built-inobject
andint
, respectively, so use those instead.In older numpy releases,
numpy.bool
was the same as Pythonbool
. This was deprecated in 1.20 and later removed for 1.x, then the namenumpy.bool
was reintroduced in numpy 2.x as an alias fornumpy.bool_
, a Boolean value stored as a byte. By usingnumpy.bool_
everywhere, we get the same data type on all Python versions.Fixes:
(Only on numpy 1.x;
numpy.bool
works on 2.x, but with a different meaning):