introduce rapids-generate-pip-constraints #114
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.
Conributes to rapidsai/build-planning#81
rapidsai/shared-workflows#228 introduced a new environment variable for wheel-testing CI jobs,
RAPIDS_DEPENDENCIES
, which takes the following values:oldest
= pin to oldest-supported versionslatest
= do not constraint versionsTo take advantage of that in CI, PRs like rapidsai/cudf#16570 have been rolling out. They're all taking a similar approach, copying around the same snippet of code that generates a pip
constraints.txt
file usingrapids-dependency-file-generator
.Based on the suggestion from rapidsai/cudf#16570 (comment), this proposes wrapping that behavior in a tool.
Notes for Reviewers
Benefits of this change
Simplifies and standardizes CI scripts.
Reduces the effort to roll out other types of testing with alternative dependency sets in the future.
How I tested this
With latest
cudf
(including the changes from rapidsai/cudf#16570) checked out, ran the following from the root of that repo: