-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
DOC: Replace .values with .to_numpy() in enhancingperf #26313
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
As suggested in pandas-dev#24807 (comment) Replace `.values` with `.to_numpy()` in the benchmark demonstration code.
Thanks for the PR! How much effort do you think it would it be to swap out all of these instances across the documentation? |
Codecov Report
@@ Coverage Diff @@
## master #26313 +/- ##
==========================================
- Coverage 92.04% 92.03% -0.01%
==========================================
Files 175 175
Lines 52302 52302
==========================================
- Hits 48142 48137 -5
- Misses 4160 4165 +5
Continue to review full report at Codecov.
|
Codecov Report
@@ Coverage Diff @@
## master #26313 +/- ##
==========================================
- Coverage 92.04% 92.03% -0.01%
==========================================
Files 175 175
Lines 52302 52302
==========================================
- Hits 48142 48137 -5
- Misses 4160 4165 +5
Continue to review full report at Codecov.
|
@WillAyd All the Took a look at the other files under |
Fix: after replacing .values with .to_numpy(), some lines are too long to pass the line-length check.
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.
Great thanks for checking. I think this looks good - @gfyoung any thoughts?
For our own edification, can those benchmark numbers be double-checked (i.e. the ones that follow the And how much better is it vs. using |
Thanks for the review. I just checked that changing to The performance comparison between |
True, but always good to double check to make sure we aren't actually proposing a performance regression in our docs. |
Thanks @huizew ! |
As suggested in #24807 (comment)
Replace
.values
with.to_numpy()
in the benchmark demonstration code.