Fix inconsistent results for pd.api.types.is_string_dtype #62112
+39
−3
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.
Description
This PR fixes an inconsistency in
pd.api.types.is_string_dtype()
when passed a Categorical series directly versus the dtype of that series.Currently:
The issue is that when a Categorical series is passed, the function correctly checks if the categories are strings, but when a Categorical dtype is passed directly, it doesn't handle it properly.
Fix
The fix adds explicit handling for CategoricalDtype in both cases (series and dtype) to ensure consistent behavior.
Test Plan
Added a new test file
test_categorical_string_dtype.py
with tests that verify the consistent behavior for both Categorical series and their dtypes.Fixes #62109