-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
DOC: Improve describe() documentation #41012
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
Conversation
Test failure seems unrelated |
@@ -176,7 +176,7 @@ these are by default not taken into account by the :func:`~DataFrame.describe` m | |||
|
|||
Many pandas operations return a ``DataFrame`` or a ``Series``. The | |||
:func:`~DataFrame.describe` method is an example of a pandas operation returning a | |||
pandas ``Series``. | |||
pandas ``Series`` (one numerical column) or a pandas ``DataFrame`` (many numerical columns). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need the column reference? Meaning is this done elsewhere in the getting started docs?
Yeah this test is flaky |
Thanks for looking at this @Bharat123rox. This patch doesn't look to be addressing the issue - the line before already says that different pandas operations might return a Series or DataFrame. The issue here is that the next line mentions that this is an example of a Series being returned, but a DataFrame is actually being returned from this describe example |
So should we just stick to this example and change it to |
I would agree with just mentioning DataFrame and Series, e.g. removing the column reference. Do you agree @mzeitlin11? |
Updated, please re-review |
Thanks @Bharat123rox |
* DOC: Improve describe() documentation * DOC: Remove Column References
* DOC: Improve describe() documentation * DOC: Remove Column References
It feels more verbose, but necessary?