-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
DOC: Docstrings Formatting Error PR09 #28602
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 am planning to work on this, specifically the
However, I need a little guidance regarding parameter descriptions. Take
The description has this bulleted list and I can't find anything in the numpy docstring or pandas docstring guides about this. Is it okay to have these lists? If so, what is the correct way to format them? If not, is it better to just have a sentence description per value? |
after reading contributing_docstring.html#section-3-parameters a little more carefully, I came up with this:
this passes the PR09 test. @datapythonista thoughts? do we care all that much how the docstrings are formatted so long as they are passing the validation? |
We care about the docstring having the right content and following the standards for consistency and correct rendering. The script is an attempt to help us with that, so we're surely not happy by the script saying that things are ok. freq got the decription where there should be the type. And the indentation of the description of ambiguous seems too much (should be 4 spaces). Feel free to improve the validation script to try to capture these problems (wrong indentation, and lack of parameter description). |
working on
|
working on pandas.DataFrame (#28702 ) |
Working on pandas.Series #28738 |
17 PR09 errors remaining in the code are listed below.
Some of these are already being worked on in open issues
|
Remaining:
|
|
Validation error
PR09 (Parameter description should end with ".")
. Removing this issue from the code base enables the addition to the CI for automated testing in the future.If you are working on this issue, it probably makes sense to check for error
PR08
in issue #25232 as well since they require similar changes.PR09
has 445 occurrences (see #27977 )Todo:
The text was updated successfully, but these errors were encountered: