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

DEPR: positional arguments in favor of keyword arguments #48735

Conversation

ambujpawar
Copy link
Contributor

@ambujpawar ambujpawar commented Sep 23, 2022

@ambujpawar ambujpawar changed the title Deprecate positional arguments in favor of keyword arguments DEPR: positional arguments in favor of keyword arguments Sep 23, 2022
pandas/core/generic.py Outdated Show resolved Hide resolved
@mroeschke mroeschke added Deprecate Functionality to remove in pandas Missing-data np.nan, pd.NaT, pd.NA, dropna, isnull, interpolate labels Sep 23, 2022
@jbrockmendel
Copy link
Member

This is currently just changing, not a deprecation.

@@ -215,6 +214,7 @@ Indexing
- Bug in :meth:`DataFrame.reindex` filling with wrong values when indexing columns and index for ``uint`` dtypes (:issue:`48184`)
- Bug in :meth:`DataFrame.reindex` casting dtype to ``object`` when :class:`DataFrame` has single extension array column when re-indexing ``columns`` and ``index`` (:issue:`48190`)
- Bug in :func:`~DataFrame.describe` when formatting percentiles in the resulting index showed more decimals than needed (:issue:`46362`)
- :meth:`DataFrameGroupBy.fillna` and :meth:`SeriesGroupBy.fillna` now allow only keyword arguments to be passed except value(:issue:`48395`)
Copy link
Member

Choose a reason for hiding this comment

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

space after value, and please use value

Also please move to deprecations

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 received contradicting review about moving/not moving to deprecations in the previous comments.

I am kinda confused now regarding which one should I actually do?

Copy link
Member

Choose a reason for hiding this comment

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

We have a section Other Deprecations where we announce all deprecations before changing behavior in a later release

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Hi, I could not find a section with the name Other Deprecations so moving it to deprecations for now.

@ambujpawar ambujpawar requested review from phofl and removed request for mroeschke October 16, 2022 19:28
@ambujpawar ambujpawar requested a review from phofl October 18, 2022 21:11
@ambujpawar ambujpawar requested review from mroeschke and removed request for phofl October 27, 2022 07:27
@mroeschke
Copy link
Member

Just noting logistically I would prefer removing all prior deprecations before adding new ones for 2.0

@jbrockmendel
Copy link
Member

Just noting logistically I would prefer removing all prior deprecations before adding new ones for 2.0

Agreed. Some of the 2.0 deprecations are missing from #30228, so we're gonna end up just grepping for FutureWarning. Adding new ones will cause trouble.

@github-actions
Copy link
Contributor

This pull request is stale because it has been open for thirty days with no activity. Please update and respond to this comment if you're still interested in working on this.

@phofl
Copy link
Member

phofl commented Jan 12, 2023

Needs a rebase, we will start merging deprecations

@@ -1075,8 +1075,8 @@ Metadata

Other
^^^^^
- Add future warnings in :meth:`DataFrameGroupBy.fillna` and :meth:`SeriesGroupBy.fillna` allowing only keyword arguments to be passed except ``value`` (:issue:`48395`)
Copy link
Member

Choose a reason for hiding this comment

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

move to section starting on L564 and reword like the others, so maybe "Deprecated...." instead of mentioning FutureWarning.

@mroeschke
Copy link
Member

Thanks for the pull request, but it appears to have gone stale. If interested in continuing, please merge in the main branch, address any review comments and/or failing tests, and we can reopen.

@mroeschke mroeschke closed this Feb 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Deprecate Functionality to remove in pandas Groupby Missing-data np.nan, pd.NaT, pd.NA, dropna, isnull, interpolate Stale
Projects
None yet
Development

Successfully merging this pull request may close these issues.

DEPR: GroupBy.fillna positional arguments
6 participants