BUG: Fix MultiIndex key type check for datetime/date (Issue #55969) #62819
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.
doc/source/whatsnew/v3.0.0.rstfile if fixing a bug or adding a new feature.This PR fixes an issue in MultiIndex where keys of type
np.datetime64would cause a silent error that could result in partial/incorrect lookups when compared to levels containingdatetime.datetime.-Added a type-check in _get_loc_level to allow compatible datetime/date types.
-Introduced a helper method _is_key_type_compatible.
-Added tests in pandas/tests/indexes/multi/test_datetime_indexing.py to cover:
--datetime.date vs datetime.datetime
--numpy.datetime64 lookups
Issue Reference
#55969