-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
CLN: .value -> ._values outside of core/ #32781
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
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
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.
In general: do we just want to always use _values
instead of values
where possible? Or do we still prefer values
in case both are not different (eg because of dealing with numeric data), in the idea of preferring a public property above a private, even in our own code base?
+1 on this, I agree we should not use |
@jbrockmendel I am fine with the general rule of not using But there are still some relevant inline comments |
@jorisvandenbossche updated the one clearly-actionable inline comment. can you point out which other comments you have in mind? (or "resolve conversation" for the complement) |
Added new comments to those that are IMO still actionable, and resolved the others |
thanks |
pandas.plotting I left alone