-
Notifications
You must be signed in to change notification settings - Fork 22
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
rip collects and tries to build packages explicitly against the users requirements #173
Comments
That is interesting, because I agree it should not even consider these versions. Also, the assertion is a bug as well. |
Oh for me its no longer an assertion on main, currently the output is:
@notatallshaw could you give it another go to see if this matches your output? |
@tdejager even with your output it tries a version of apache-beam that conflicts with the second spec though. |
Yeah I know, I just want to know it the assertion is gone ;) |
I'll have a look if I can create a reproducer in Resolvo. |
This is a user error 🤦♂️ . The following installs fine:
The following:
Attempts to install The fact that the latter fails to install is better covered by #174 Sorry for wasting your time. I think I missed this because the output wasn't captured into the new file (is logging on stderr or something?). |
Also, I retested on main and am no longer getting this assertion error. |
Great! The funny thing was I thought: "Oh does that work without quotes" 🤦 😄 |
Environment: Linux Python 3.11
Command:
cargo r -- apache-airflow[all]==2.8.1 apache-beam>=2.47
Error:
Expected Behavior: rip should not have even collected
apache-beam 2.42.0
as the requirement explicitrly statedapache-beam>=2.47
If this was collected because it was an sdist build requirement (I don't think so? But it's hard to tell from the logs), then I think rip must provide a way to constrain build requirements.
The text was updated successfully, but these errors were encountered: