-
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
Remove RequirementSet.require_hashes #7068
Remove RequirementSet.require_hashes #7068
Conversation
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.
A couple comments. Also, a question: do we know that resolve()
is only called once?
Right now, yes. I think it's reasonable to expect that to stay true going forward but I do prefer if we defer making that choice until we see that as being something that causes functional issues. |
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 |
Removes the only dynamic state from Resolver, at the cost of passing an extra variable to 2 methods.
This removes some of the dependence of the Resolver on our specific RequirementSet implementation.
a47803f
to
b8fb97a
Compare
Updated and ready for review. Since there is now no state being changed within |
The purpose of this change is two-fold:
Resolver
andRequirementSet
, towards the goal of havingResolver.resolve()
accept a plainIterable[InstallRequirement]
RequirementSet
itself, since after build refactoring it should not need to existThis does add one parameter to
Resolver
, however in later refactoring we should be able to encapsulate all of the hash-related logic in an object thatResolver
would use to query for and prepare requirements.