-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
"No solution found when resolving dependencies", but pip installs readily #2538
Comments
Well, of course I tried again after creating the issue and it worked immediately. I conclude that uv caches results with a TTL of something like 5-10 minutes. Is that right? |
Yep there's a 10 minute cache, I'd recommend using |
Fabulous. I'm happy with the choice. Two comments/suggestions/questions (and I'm happy to help):
|
(1) "Could not be satisfied" has a bit more of a complex meaning, like "this version exists but its requirements cannot be reconciled with the solution". I'm pretty hesitant to change the wording there since in most cases the version actually will not exist. We could do something like.. find all the versions that "do not exist" in a resolution tree and check if it exists with caching disabled then add hints or mutate the message in that case. This would slow down display of the error report but we worry less about performance once you're in an error case. (2) I worry changing the behavior based on version specifiers, it seems confusing. A simple policy is my preference. |
Same when installing torch
Now the same with pip
uv needs to be explicitly provided with |
@yashgorana - I think that's unrelated, and covered in the pip compatibility guide: https://github.com/astral-sh/uv/blob/main/PIP_COMPATIBILITY.md#local-version-identifiers |
Aha - thank you for pointing to the docs! |
Np. The local version support is relatively new. There's also an open issue here to track improving it further to remove the existing limitations: #2541 |
I got the same error, in a different situation, using Linux. |
uv does recognize manylinux packages when using |
|
And you can get this to work with pip? |
A lot of this looks correct to me... You're using Python 3.10, and so the only versions you're allowed to use from that index are 1.24.3, 1.24.4, and 1.26.4, because they don't publish Python 3.10 wheels for any other versions. |
Yes. There are wheel of numpy in this URL only works for Python 3.10, and with pip it install correctly.
|
The problem is that they have multiple wheels for the same version with different metadata on that registry. For
The former requires We require metadata to be consistent across wheels. I guess we could try to select the wheel with the higher build number but I'm not sure that's standardized. I'll look. |
It looks like it is standardized so I'll create a separate issue for it: https://peps.python.org/pep-0427/#file-name-convention |
Fixed in #3781, thanks. |
Summary: uv pip install fails to install a package that pip installs without issue. The package is an alpha release that I pushed to pypi a few minutes ago.
The text was updated successfully, but these errors were encountered: