POC: pd.Scalar #62456
Open
POC: pd.Scalar #62456
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
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.
xref #42349
Motivated by the discussion on yesterday's dev call about #62423, I think we eventually need something to indicate "treat this sequence as a scalar". That can either be
pa.scalarif we eventually require pyarrow orpd.Scalarthat this PR implements.This PR implements a deprecation in Categorical comparisons as an example of a motivating use case. If we decide to go down this road, handling for it will need to be added in a bunch of places, kind of like
lib.item_from_zerodim.Update In case it wasn't obvious, this is definitely not for 3.0.