-
Notifications
You must be signed in to change notification settings - Fork 38
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
Merge custom incompatibility reasons #232
Comments
4 tasks
@Eh2406 you may be interested in astral-sh/uv#6154 — to get started, I'm implementing the collapse on the derivation tree instead of in the resolver. |
zanieb
added a commit
to astral-sh/uv
that referenced
this issue
Aug 16, 2024
Uses my expanding tree reduction knowledge from #6092 to improve the long-standing issue of verbose messages for unavailable packages. Implements pubgrub-rs/pubgrub#232, but post-resolution instead of during resolution. Partially addresses #5046 Closes #2519
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When two versions of a package have the same dependency we merge that into one incompatibility in
merge_incompatibility
. This allows us to avoid saying "Because a==1.0.0 depends on b>2 and you have b==1 and because a==1.1.0 depends on b>2 and you have b==1, ..." and skip directly to "Because a>=1.0.0 depends on b>2 and you have b==1, ..". Pubgrub should perform the same merging for custom incompatibilities.Here's a shortened example, the full error message is 200 lines long, most of which are just telling me that tensorflow is missing compatible wheels for a version range:
I can create a reproducible example if it's required.
Ref astral-sh/uv#2519
The text was updated successfully, but these errors were encountered: