-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
DOC: Fix quotes position in Timestamp and Timedelta #24070
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
Hello! May I work on this issue? |
Yes please, let me know if you need help. |
Thanks @datapythonista, I will! |
Hi! @datapythonista, I see that methods that do not have docstrings also return errors GL01 & GL02. I assume resolving this issue also involves adding in docstrings for these methods? |
no, if I'm not wrong we merged a PR today that makes the methods without a docstring generate a different error. If we didn't merge it yet, we should merge it soon |
Got it, thanks! |
Can you give me a little help please? I can't seem to clear the error even with the correct format. For example, in the file '\pandas_libs\tslibs\timedeltas.pyx':
still returns the errors:
Can you give me a little tip please? |
This file is a |
Thank you for your quick reply! I am new to python so I didn't know about pyx files. I will try to have a PR ready by tonight :) |
I will try this one. |
To keep out docstrings consistent, and make them easier to read, we try to keep always the same exact format. In the case of the opening and closing quotes, the right format is:
But for historical reasons, we have many docstrings with different format, for example:
Besides being inconsistent, having docstrings with the wrong format doesn't let us start validating and enforcing automatically the wanted format. So, we need to change all the wrong cases.
For this issue, all the wrong cases of methods of
Timestamp
andTimedelta
should be fixed. The list can be obtained with the next command (the command should not report any error when this is fixed):The text was updated successfully, but these errors were encountered: