-
Notifications
You must be signed in to change notification settings - Fork 590
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(pandas): make case work for non-RangeIndex dataframes #9083
fix(pandas): make case work for non-RangeIndex dataframes #9083
Conversation
e5f99d5
to
a3c59cc
Compare
|
What's the use case that's enabled here that requires this change? What can you not do with the current codebase? |
register a dataframe with non-range index and have cases work |
|
alternatively, should dataframes' index be sanitized on registration? is there a specification of what should be true about dataframes that are registered? |
It would be good to have a less abstract example documented in this PR. Doesn't really even have to be code, just some description that helps justify why we should take on any additional code to the pandas backend. |
Does this match what you're looking for? When I run this code I get these results |
|
Heh, yeah, that does :) I'll just keep suggesting that the pandas backend should probably be avoided. I somewhat reluctantly will accept this PR, fully realizing that creating the pandas backend was probably a doomed idea from the start 😂 |
Description of changes
This PR makes
PandasExecutorcreate theSerieswith an index that matches the incoming data. Currently, when the incoming data does not use aRangeIndex, the output index is a union of aRangeIndexand the incoming data index.