DOC: clarify .str behaviour on mixed-type Series #64061
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What does this PR do?
Adds a short clarification to the user guide explaining the behaviour of
pandas string methods on mixed-type Series.
In particular, it documents that
.strmethods are applied element-wiseand that non-string values result in
NaNrather than raising an error.An example is included to illustrate this behaviour.
Why is this needed?
This behaviour is intentional but can be surprising to new users.
It commonly leads to confusion when working with mixed-type data,
especially around
NaNpropagation and output dtypes.This change improves discoverability and understanding without changing
any existing behaviour.