-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Correctly resolve requirement requested both as non-extra URL and non-URL with extras #9775
Correctly resolve requirement requested both as non-extra URL and non-URL with extras #9775
Conversation
Note to self: #9644 should be able to be fixed with 0.6.0. Probably in a separate PR though, need to investigate. |
f8b84c7
to
c02f0b6
Compare
This comment has been minimized.
This comment has been minimized.
c02f0b6
to
b4fb4f2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did a read-the-diff review, and this looks good to me!
b972040
to
6b22212
Compare
I'm not familiar enough with the new resolver to do a meaningful review, so I'm going to merge this soon for 21.1 based on approvals and reputation. Holler if this is not ready for any reason. |
Hello! I am an automated bot and I have noticed that this pull request is not currently able to be merged. If you are able to either merge the |
When a requirement is requested multiple times, some via a direct URL ("req @ URL") and some not but with extras ("req[extra] VERSION"), the resolver previous could not correctly find "req[extra]" if "req" is available in an index. This additional logic makes the resolver, when encountering a requirement with identifier "req[extra]", to also look for explicit candidates listed under "req", and add them as found matches for "req[extra]".
6b22212
to
0305e0d
Compare
I added a commit to refactor |
8c2d448
to
febe770
Compare
febe770
to
9cab983
Compare
@uranusjr CI is red. |
That xdist bug again... |
Also moves the incompatibility candidate calculation to closer to their usages.
This seems to work fine. Is it good to go for you @uranusjr ? |
Yup, feel free to merge 🙂 |
Shouldn't be needed in pip >= 21.1. pypa/pip#9437 pypa/pip#8785 pypa/pip#9775
Fix #8785. This depends resolvelib 0.6.0 and needs #9771 to be merged first.