-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
uv add onnxruntime
currently fails on MacOS
#9228
Comments
Ah yeah. This is working as intended right now. |
(I'm going to combine with #5182 since it's ultimately the same problem as with PyTorch.) |
Thanks for the very fast reply, I now understand the challenge. I will track the other gh issue and add a constraint for now. Thanks! |
Thanks @reyammer. I promise it's a hard problem 😂 But I'd like to make the situation better here. |
oh I fully believe you 😂 what confused me is that pip worked well this time, but given your note it seems there are cons in doing whatever pip is doing. Anyways, no big deal, added an upper bound for onnxruntime and everything now works as expected. Thanks again! |
I've the same problem as well with python 3.12,
@reyammer I've kept the version at |
Hello,
Running
uv add onnxruntime
in a newuv
repo currently fails on MacOS. The installation works withpip
.Commands:
$ uv init
$ uv add onnxruntime
Output:
Platform: MacOS, 12.5
uv version: 0.5.2.
More context, which hopefully helps debugging:
pip install onnxruntime
works; the catch seems to be that it installs onnxruntime 1.19.2.uv add magika==0.6.0rc2
fails (referencing "can't find a proper wheel for onnxruntime 1.20.0"). On the same platformpip install magika==0.6.0rc2
works (by picking onnxruntime 1.19.2). Another way to make it work is:uv add onnxruntime==1.19.2; uv add magika==0.6.2rc2
).The gist of the problem seems to be that onnxruntime 1.20.0 is not compatible with the MacOS, but uv quits instead of trying with 1.19.2, which is compatible.
Happy to help debugging this, I'm a massive uv fan!
The text was updated successfully, but these errors were encountered: