Skip to content
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

ImportError raises 1.11 while check is for 1.15 #1068

Closed
praateekmahajan opened this issue Sep 10, 2024 · 4 comments · Fixed by #1069
Closed

ImportError raises 1.11 while check is for 1.15 #1068

praateekmahajan opened this issue Sep 10, 2024 · 4 comments · Fixed by #1069

Comments

@praateekmahajan
Copy link

praateekmahajan commented Sep 10, 2024

The check is for 1.15 however the error message raised is that 1.11+ is required.

Bonus ask, it'll be great if we can show the path of the library that's being loaded and checked so that we can debug further if it's system library or environment library.

ucx-py/ucp/__init__.py

Lines 113 to 117 in 2ba56e5

if get_ucx_version() < (1, 15, 0):
raise ImportError(
f"Support for UCX {__ucx_version__} has ended. Please upgrade to "
"1.11.1 or newer."
)

@pentschev
Copy link
Member

What does get_ucx_version() print on that system?

@praateekmahajan
Copy link
Author

Hey @pentschev my get_ucx_version returns 1.13.0. Also sorry linked the wrong code from 0.39 branch, updated it now to indicate the 0.40 which is being pulled in for nightly.

@pentschev
Copy link
Member

I've addressed this in #1069 , I'm not going to spend time on meddling with library loading mechanism to extract the path where UCX is being loaded from, but I did add to the exception instructions on how to properly do that with UCX log levels.

@pentschev
Copy link
Member

Addressing the same in UCXX via rapidsai/ucxx#277 .

@rapids-bot rapids-bot bot closed this as completed in 229b6a0 Sep 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants