-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
BUG: Fix skipna
default value in method signatures
#43980
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
BUG: Fix skipna
default value in method signatures
#43980
Conversation
I did not change the mad method, since its signature matches the docstring and the implementation. Changing that one would require a deprecation cycle I guess; if not, let me know and I will amend the commit. |
yeah this is fine |
looks fine. @jbrockmendel ok here? |
could remove the |
Realizing here that I may have left behind many of them in private functions, e.g. https://github.com/pandas-dev/pandas/pull/43980/files#diff-1a2e3df0db7dd8bddc2ec4bff9de8a7a55e328e6c32e2cecde761dc9549fcd46R10390 etc. There are still 10 (+2 corresponding to the Are these 10 supposed to be changed as well ? |
@jreback @jbrockmendel any suggestion as to what I should do concerning #43980 (comment) ? Thanks. |
see if you break anything by changing them. IIRC we did this for some backwards compat but that was quite a while ago. |
Set `skipna` default values to `True` so that the value matches the purpose of the variable and its docstring.
👍 Push-forced in e15a1ce. Let's see what the CIs say. |
thanks @jhlegarreta very nice! |
Set
skipna
default values toTrue
so that the value matches thepurpose of the variable and its docstring.