Skip to content

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

Merged
merged 8 commits into from
Mar 21, 2020

Conversation

jbrockmendel
Copy link
Member

pandas.plotting I left alone

Copy link
Member

@WillAyd WillAyd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@WillAyd WillAyd added the Clean label Mar 18, 2020
Copy link
Member

@jorisvandenbossche jorisvandenbossche left a 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?

@jreback jreback added this to the 1.1 milestone Mar 19, 2020
@jreback
Copy link
Contributor

jreback commented Mar 19, 2020

+1 on this, I agree we should not use .values at all; agree that using np.asarray() when we actually need a numpy arra (or .to_numpy()) explicitly is nice too. In an ideal world, we never should use .values and we can then maybe deprecate on the user side.

@jorisvandenbossche
Copy link
Member

@jbrockmendel I am fine with the general rule of not using .values. Although I think in cases where we explicitly need a numpy array, we should rather use asarray / to_numpy.

But there are still some relevant inline comments

@jbrockmendel
Copy link
Member Author

@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)

@jorisvandenbossche
Copy link
Member

jorisvandenbossche commented Mar 20, 2020

Added new comments to those that are IMO still actionable, and resolved the others

@jreback jreback merged commit f0fc6dd into pandas-dev:master Mar 21, 2020
@jreback
Copy link
Contributor

jreback commented Mar 21, 2020

thanks

@jbrockmendel jbrockmendel deleted the no-values-non-core branch March 21, 2020 21:10
SeeminSyed pushed a commit to CSCD01-team01/pandas that referenced this pull request Mar 22, 2020
jbrockmendel added a commit to jbrockmendel/pandas that referenced this pull request Mar 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants