-
Notifications
You must be signed in to change notification settings - Fork 1.1k
refactor: use libnvcomp from libkvikio wheel to unblock Python 3.13 upgrade
#18593
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
rapids-bot
merged 17 commits into
NVIDIA:branch-25.06
from
gforsyth:libkvikio_vendor_nvcomp
May 2, 2025
Merged
Changes from all commits
Commits
Show all changes
17 commits
Select commit
Hold shift + click to select a range
569295a
[DO NOT MERGE]: test upstream libkvikio wheel with vendored nvcomp
gforsyth 9b40d9f
bucket path
gforsyth 30073fe
tarball and wheel have different suffixes
gforsyth 0626b60
update sha and version suffix for updated kvikio
gforsyth c9f7402
make sure we use the updated kvikio wheel everywhere
gforsyth 66b507e
cleaner downloading of artifacts from kvikio PR
gforsyth c0af5c7
disable using nvcomp runtime wheel
gforsyth c351029
Revert "cleaner downloading of artifacts from kvikio PR"
gforsyth 8e5378a
Revert "disable using nvcomp runtime wheel"
gforsyth 97faca6
try to fix install paths
gforsyth 6e75249
update libcudf RPATH for libkvikio-bundled nvcomp
gforsyth 3121d4e
don't export nvcomp
gforsyth a3d9625
make sure upstream libkvikio is installed for pandas and polars tests
gforsyth d39e41a
and again
gforsyth 8970333
yet another spot to constrain install
gforsyth b16cbe6
refactor: use upstream nightly wheel for libkvikio+nvcomp
gforsyth 8f9990d
Merge branch 'branch-25.06' into libkvikio_vendor_nvcomp
gforsyth File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Just putting this in writing to make it explicit... I think it's ok to allow
USE_NVCOMP_RUNTIME_WHEELand andUSE_NVCOMP_FROM_LIBVIKIO_WHEELto both beON, as you've done here.Having both RPATHs set on
libcudf.so, even if accidentally, shouldn't be a problem. But just calling out that possibility, to give you an opportunity to say "oh yeah, I hadn't thought of that... ok no that's bad, let's make them mutually exclusive".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.
That's a good callout -- I do think that it's ok if they're both set. It should be a temporary addition, in any case.