Change check() function to test actual types in Series and Index #546
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.
While reviewing #372 , it uncovered that by having
check()
usenext(iter())
, if you have aSeries([1,2,3], dtype=np.int8)
, it was not checking that the actual type of the first element wasnp.int8
, sinceSeries.__iter__()
returns a python scalar.So this corrects that, allowing us to be more precise in the type checking of the values inside the results, since we want to check that
astype()
is doing what we expect.Also, was able to allow
pytables
to work with 3.11, since they released a compatible version.Uncovered an odd issue with bitwise operations on lists of
int
In some cases, used
np.integer
because it is a supertype that works across platforms. Other times,np.int_
worked fine.