DOC: Clarify that is_scalar treats Enum members as scalars #62132
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 updates the
is_scalar
docstring to clarify that Enum members are treated as scalars, addressing the confusion reported in #62063.The
is_scalar
function already correctly treats Enum members as scalars (viaisinstance(val, Enum)
in the implementation), but the documentation was unclear about this behavior, leading to confusion for users and type checkers.Changes Made
list
,tuple
,numpy.ndarray
, andpandas Series
are considered non-scalarChecklist