publish v1.14.1.post1#6
Conversation
jameslamb
added
bug
|
No opposition from me if there's a specific use case, but notice that we don't support 1.14.x anymore, see https://github.com/rapidsai/ucx-py/blob/c1c34669d5b295c0d5f260e3c38de1dfe00efb32/dependencies.yaml#L118-L120 and https://github.com/rapidsai/ucx-py/blob/c1c34669d5b295c0d5f260e3c38de1dfe00efb32/conda/recipes/ucx-py/meta.yaml#L38, the same is true for UCXX. |
|
Oh ok, thank you! I'll let @vyasr comment, but I think we're looking to patch every If you're curious, you can see the versions that have been published at https://pypi.anaconda.org/rapidsai-wheels-nightly/simple/libucx-cu12/ 
Which makes me realize... this should really be |
|
Yup James is right, the goal here is to supersede the first round of wheels (even for versions of libucx that RAPIDS isn't using) so that we don't publish broken libraries. |
Follow-up to #5. Similar to #6. Proposes publishing a `1.16.0.post1` version, identical to version `1.16.0` except that `load_library()` will no longer raise exceptions in non-GPU environments. ## Notes for Reviewers Checked https://pypi.anaconda.org/rapidsai-wheels-nightly/simple/libucx-cu12/ to confirm that it's exactly `1.16.0` that we want to do a post-release for.
3 participants
Follow-up to #5.
Proposes publishing a
1.14.1.post1version, identical to version1.14.1except thatload_library()will no longer raise exceptions in non-GPU environments.Notes for Reviewers
Just putting this up to get in the CI run. Should probably wait to merge it until testing on rapidsai/ucx-py#1041 is done.