Skip to content
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

Ensure column.fillna signatures are consistent #14724

Merged
merged 4 commits into from
Jan 10, 2024

Conversation

mroeschke
Copy link
Contributor

Description

Aligns the definitions of Columns.fillna among all subclasses. dtype looks to only needed in certain instances to cast the fill value so can do that separately. A fill_nan can be avoided with its single usage in a can_cast routine by checking for nan first

Checklist

  • I am familiar with the Contributing Guidelines.
  • New or existing tests cover these changes.
  • The documentation is up to date with these changes.

@mroeschke mroeschke added Python Affects Python cuDF API. improvement Improvement / enhancement to an existing function non-breaking Non-breaking change labels Jan 8, 2024
@mroeschke mroeschke requested a review from a team as a code owner January 8, 2024 23:24
method: Any = None,
dtype: Optional[Dtype] = None,
) -> CategoricalColumn:
method: Optional[str] = None,
Copy link
Contributor

@bdice bdice Jan 9, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just checking -- this is non-public so the API break of dropping dtype is not a "breaking change" right?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've been working under that assumption that cudf column objects are not public cc @shwina

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, that should be fine! Just wanted to check in case this interacts with any future changes you were planning for public types.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Gotcha. Yeah the arguments being modified in Column.fillna do not clash with Series/DataFrame.fillna

@mroeschke
Copy link
Contributor Author

/merge

@rapids-bot rapids-bot bot merged commit 6a23775 into rapidsai:branch-24.02 Jan 10, 2024
67 checks passed
@mroeschke mroeschke deleted the ref/column/fillna branch January 10, 2024 01:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
improvement Improvement / enhancement to an existing function non-breaking Non-breaking change Python Affects Python cuDF API.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants