-
Notifications
You must be signed in to change notification settings - Fork 916
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
More explicit index concat checking #15650
base: branch-24.06
Are you sure you want to change the base?
More explicit index concat checking #15650
Conversation
@wence- for visibility |
/ok to test |
I would suggest that we introduce this change in behaviour by adding an appropriate deprecation, we can then fix up any internal usages and remove in a subsequent release. |
this isn't a change in behavior. this is how the library already behaves. the difference here is we more explicitly raise the issue to the user instead of providing them with a more ambiguous error message |
Ah, I misread, sorry. WDYT about the idea as well as deprecating all |
@wence- that seems reasonable to me and i'll proceed with that, thanks! |
@wence- also, i don't think the 'breaking' tag is appropriate for this PR? WDYT? |
/ok to test |
Cross-linking for info: #15649 (comment) |
draft mode until i can work through 2, 3, 4, & 5 listed here: #15649 (comment) |
…oncat-index-behavior-diverts-from-pandas
Description
Closes #15649
We allow concatenating indexes whilst
pandas
does not. Currently, this PR would more explicitly raise issues that already exist withaxis=1
index concatenation to users. We would also expose a deprecation warning for the eventual removal of index concatenation forpandas
parity.Checklist