You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe. #14156 introduces an upper bound pinning to numpy because version 1.25 deprecates some core functionality that we use, namely np.find_common_type.
Describe the solution you'd like
We should refactor our internals to remove usage of this deprecated function, then remove the pin.
Describe alternatives you've considered
None
Additional context
pandas also uses this function internally and therefore will emit warnings when used with a newer numpy. This is fixed in pandas 2.0, but the fixes are not being backported, so we can't fully resolve this issue until cudf also switches to supporting pandas 2.x.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
#14156 introduces an upper bound pinning to numpy because version 1.25 deprecates some core functionality that we use, namely
np.find_common_type
.Describe the solution you'd like
We should refactor our internals to remove usage of this deprecated function, then remove the pin.
Describe alternatives you've considered
None
Additional context
pandas also uses this function internally and therefore will emit warnings when used with a newer numpy. This is fixed in pandas 2.0, but the fixes are not being backported, so we can't fully resolve this issue until cudf also switches to supporting pandas 2.x.
The text was updated successfully, but these errors were encountered: