-
Notifications
You must be signed in to change notification settings - Fork 915
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
[REVIEW] Upgrade cudf
to support pandas
1.4.x versions
#10584
Conversation
Codecov Report
@@ Coverage Diff @@
## branch-22.06 #10584 +/- ##
================================================
- Coverage 86.40% 86.31% -0.10%
================================================
Files 143 143
Lines 22448 22514 +66
================================================
+ Hits 19396 19432 +36
- Misses 3052 3082 +30
Continue to review full report at Codecov.
|
Co-authored-by: Bradley Dice <[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.
Thanks @galipremsagar! I replied above on one question about numpy pinning. Otherwise LGTM.
rerun tests |
2 similar comments
rerun tests |
rerun tests |
@gpucibot merge |
…behavior (#10749) Fixes #10618 Depends on #10584 Authors: - Karthikeyan (https://github.com/karthikeyann) Approvers: - GALI PREM SAGAR (https://github.com/galipremsagar) - Yunsong Wang (https://github.com/PointKernel) URL: #10749
This PR:
pandas
version to1.4.x
shift
when the fill_value is not of same type.CategoricalColumn.fillna
if there is a mismatch of dtypes, the error is changed toTypeError
fromValueError
skina
for a number of operations toTrue
fromNone
.RangeIndex.sort_values
for API compatibility and avoiding materializations.Series
constructor wherename
parameter was not being used when passed explicitly.name
handling inSeries.reset_index
to match pandas behavior.Prev:
Now: