-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
DOCS: Update import statements in docstrings #21749
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
What's this for? |
This is related to this.. #21731 (comment) |
@TomAugspurger : I've updated the issue to clarify the purpose. |
I modified the import statements in the following files from the list in the OP and some others:
but kept these intact..
Do you think we should These were modified in a different PR
|
Do we have an idea which of these are still relevant? |
Take |
Hello, I was wondering if it's okay to take on this issue because I noticed that some statements still use the old form |
reopening as I don't think the linked PR closes all the items |
@salomondush Are you still working on this, as I wanted to work on this issue? |
I worked on some parts of it, but you can take the remaining check points |
@salomondush Thank you so much this is my first time contributing to a big project. I might need your guidance. |
take |
@salomondush Hey, Can you tell me how did you find the exact location of docstrings that require fix? I followed the file path but didn't found those import statements that require fixing. |
Most of them have been fixed, but if you use VS code, you should be able to search specific lines of code throughout all files. |
I will modify the documents in |
I'm addressing the following import update in the PR above: ./pandas/core/algorithms.py|1519 col 5| >>> from pandas.api.extensions import take That's the only outdated import statement I could find. Does this mean all others have been addressed? Thanks! |
Appears like #45841 closed the last of the above checklist. Closing, but if there are other leftover, individual issues can be opened instead |
xref #21731 (review)
The text was updated successfully, but these errors were encountered: