-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
DOC: Do not mention private classes in the documentation #26981
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
@datapythonista Can I take this issue? |
Yes please, go for it. Thanks! |
Hi @datapythonista , I have pulled a request. This is my first time to do the code review on the Github and found there is no reviewer in my request. Do I need to find someone to review my code or just wait? |
You just need to wait, we'll review when we're free. I see you replaced NDFrame by DataFrame. That's a bit misleading, since the referred objects can also be Series (NDFrame is the parent class of both Series and DataFrame). Sorry if that wasn't clear in the issue description. Can you have a look and make sure we're not having inaccurate information with the change please? Other than that looks great. |
@datapythonista , Sorry for the misunderstanding, I will fix that tomorrow. Replace with |
The public documentation shouldn't mention private classes, which the users are not expected to know about, and they could be removed in the future without proper deprecation.
We've got a script to find them, it can be run with
./scripts/validate_docstrings.py --errors=GL04
Currently there are those cases:
I'd say in most cases we can replace
NDFrame
bySeries or DataFrame
but may be we can rephrase sentences too.After all them are corrected, we should add to
ci/code_checks.sh
the codeGL04
to the part where we validate the documentation, so the CI checks for it, and mentions toNDFrame
or other private classes are not reintroduced. Also in the same PR we can addGL05
, which is not validated but there are no errors in the code for it, so we can start validating it.The text was updated successfully, but these errors were encountered: