-
Notifications
You must be signed in to change notification settings - Fork 765
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
Confusing error message when a constraint is the cause of not finding a version #2065
Comments
Ah interesting, thanks for the report! I'm not entirely sure why these constraints are not represented in the resolver (and subsequently the error report). |
Interesting is that while the message is confusing, the hint is correct in this case - adding
When you run the
|
Don't focus on the prerelease part of the error, I've reported that separately and it's already fixed: #2063 After the next release of uv I'll see if I can come up with another example. |
Okay, now there's a release with the other fix my steps to reproduce don't work. Here are a new set of steps to reproduce: Environment: Linux Python 3.10.13 uv 0.1.14
You get the error:
The confusing part is |
Environment: Linux Python 3.10.13 uv 0.1.12
Steps to reproduce:
wget https://raw.githubusercontent.com/apache/airflow/constraints-2.3.4/constraints-3.10.txt
echo "apache-airflow==2.3.4" | uv pip compile - --constraint constraints-3.10.txt
Error:
This is confusing because
cattrs==22.1.0
doesn't depend only onexceptiongroup==1.0.0rc8
and furtherapache-airflow==2.3.4
does not depend only oncattrs==22.1.0
, as you will see if you compieapache-airflow==2.3.4
orcattrs==22.1.0
or both of them together.There is no mention that it is a user constraint which caused this failure, I beleive pip does mention when a top level user requirement or constraint caused the failure.
The text was updated successfully, but these errors were encountered: