-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
DOC: inconsistent docs-string signatures for shared functions #15609
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
Comments
I searched for **kwargs on
I have expanded the signatures for: I do not understand why round has the need for **kwargs (I read this http://book.pythontips.com/en/latest/args_and_kwargs.html at work this morning but I guess I have to read it again?). fillna seems to have the signature fully written. Similar question, why do we have **kwargs then? dropna: series.py says that the doc-string is coming from transpose: I don't know where the doc-string is coming from, so I did not edit it. Any thoughts? |
|
Yes, that is correct. Annoying? Yes. Necessary? Debatable, but there was enough push early on from users for this to be implemented. |
@PukkaPad btw, certainly ok to submit this in several PR's. |
Ok, cool! I will submit the PR now - I will make the PR smaller next time if the commit is too big. |
Hi @jreback , does this still need to be done ? I would like to take this on. |
take |
this should be closed, the issue is no longer there |
xref #15580
related to this is our inconsistent treatment of the actual args in shared doc strings, e.g.
so the following have exactly the same arguments to the doc-string (except for the first 1-2 which are the axes: index, or index & columns).
The doc-strings themselves are correct, but the signature are hidden. I think easiest is simply to actually list out the args where they are defined (e.g in
core/series.py
for example).There are a bunch of functions like this.
The text was updated successfully, but these errors were encountered: