-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
DOC: Harmonize column selection to bracket notation #27562
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
Conversation
+1 to generally using getitem in the docs, other than the section describing dot access. Can we think of a way to lint this, to ensure that we don’t regress on it in the future? I’m struggling to think of an easy way. A slightly harder way is to check for dot access of names that are in the columns with a python program run on the docs. |
I'd be +1 for making this change comprehensively |
I will not be able to write python code to detect those occasions. Using
Shall I also update old |
I think ignore old whatsnews for now - we usually don't go back and change them |
OK, I hope I didn't overlook any of these changes' context to explicitly mention "dot" notation/access/attribute. |
In order to add a |
Don’t need a whatsnew for doc changes. Also can just point to master - We can back port to 0.25.1 if needed (though not sure we would for this) |
No need for back port. |
OK :-) Anything else to do here, then besides fixing those CI errors? Maybe a note recommending [ bracket ] notation (or summarising its advantages)?
|
I'll run the checks locally with |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no objection to most of these changes, but some need to be reverted as indicated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! Some additional comments
Co-Authored-By: Joris Van den Bossche <[email protected]>
Co-Authored-By: Joris Van den Bossche <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Thanks @katrinleinweber! |
You're welcome! Thanks to you though, for agreeing with this & for merging :-) |
* Harmonize column selection to bracket notation As suggested by https://medium.com/dunder-data/minimally-sufficient-pandas-a8e67f2a2428#46f9
* Harmonize column selection to bracket notation As suggested by https://medium.com/dunder-data/minimally-sufficient-pandas-a8e67f2a2428#46f9
As suggested by @tdpetrou. If there is agreement about not presenting the dot notation to access columns in the docu, please let me know and I'll then check the rest of the docu.
black pandas
git diff upstream/master -u -- "*.py" | flake8 --diff
git diff upstream/master -u -- "*.rst" | flake8-rst --diff