Skip to content

DOC: Fix SA04 errors in docstrings #28792 #32182

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

Merged
merged 3 commits into from
Mar 3, 2020

Conversation

AdrianMastronardi
Copy link
Contributor

@AdrianMastronardi AdrianMastronardi commented Feb 22, 2020

@jreback jreback added the Docs label Feb 23, 2020
@@ -942,7 +942,8 @@ def argmax(self, axis=None, skipna=True, *args, **kwargs):

See Also
--------
numpy.ndarray.argmax
Copy link
Member

Choose a reason for hiding this comment

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

@datapythonista is this a convention we're moving to?

Copy link
Member

Choose a reason for hiding this comment

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

Hmm yea can be pretty repetitive /tedious but I don’t think there’s a way around it with the current docstring validation unless @datapythonista knows otherwise

Copy link
Member

Choose a reason for hiding this comment

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

In this case my preference would be to leverage the context of the page we are in, and have as a description something like "Same function for numpy arrays.".

But I personally think that it adds value to have the elements in the see also, and a short comment on why they are related. I'm thinking on a new user visiting head, and how helpful it can be to know that a tail method exists, and that it "does the same as head but from the end of the dataframe".

Would you prefer to not have the descriptions?

Copy link
Member

@WillAyd WillAyd left a comment

Choose a reason for hiding this comment

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

Lgtm

@WillAyd
Copy link
Member

WillAyd commented Feb 27, 2020

@AdrianMastronardi looks like a merge conflict - can you merge master?

@AdrianMastronardi
Copy link
Contributor Author

@WillAyd merge conflict resolved.

@WillAyd WillAyd added this to the 1.1 milestone Mar 3, 2020
@WillAyd WillAyd merged commit 68603b1 into pandas-dev:master Mar 3, 2020
@WillAyd
Copy link
Member

WillAyd commented Mar 3, 2020

Great thanks @AdrianMastronardi !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants