-
Notifications
You must be signed in to change notification settings - Fork 889
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
Use <NA> instead of null to match pandas. #13415
Conversation
This PR can target 23.08 but we don't have forward mergers from 23.06 to 23.08 yet and this depends on recent changes on edit: forward mergers were fixed, this can target 23.06 or 23.08 now. |
This changes behavior (column names are different) so I marked it as @shwina @galipremsagar Do you think this should go in for 23.06 or 23.08? We have the opportunity to exactly match pandas behavior by merging this (in conjunction with the merged changes from #11656). |
Okay to target for 23.06 since this is a bug fix. But will wait on @shwina to comment too. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Going to go ahead and merge
/merge |
1 similar comment
/merge |
Description
This PR updates the behavior of one-hot encoding to use
<NA>
for null values rather thannull
. This aligns with pandas behavior.This change is backported from #13174 since it applies to pandas 1.x as well as pandas 2.0.
Checklist