-
-
Notifications
You must be signed in to change notification settings - Fork 18.1k
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
DOC: Enforce Numpy Docstring Validation | pandas.Datetime #58066
Comments
Taking:
|
4 tasks
Will work on:
|
Working on |
5 tasks
5 tasks
working on
|
5 tasks
working on
|
5 tasks
working on
|
5 tasks
working on
|
1 task
5 tasks
Working on
|
working on
|
Now working on
|
5 tasks
This was referenced Apr 25, 2024
working on
|
working on
|
This was referenced Apr 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
DOC: Enforce Numpy Docstring Validation (Parent Issue) #58063
Pandas has a script for validating docstrings in code_checks.sh. Currently, some methods fail some of these checks.
pandas.Datetime
pandas/ci/code_checks.sh
Lines 135 to 167 in c468028
The task is:
take 1-5 methods
run:
scripts/validate_docstrings.py --format=actions <method-name>
example command:
scripts/validate_docstrings.py --format=actions pandas.Categorical.__array__
example output:
check if validation docstrings passes for those methods, and if it’s necessary fix the docstrings according to whatever error is reported. Note: We've chosen to ignore ES01 errors, these are not required to be fixed.
remove those methods from code_checks.sh if all errors are cleared and the docstring is correct, otherwise, remove the specific error that was fixed from the list of errors for that method.
commit, push, open pull request
Please don't comment
take
as multiple people can work on this issue. You also don't need to ask for permission to work on this, just comment on which methods are you going to work : )If you're new contributor, please check the contributing guide
thanks @datapythonista for the inspiration for this issue!
The text was updated successfully, but these errors were encountered: