Make direct dependency detection respect markers #2207
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
When determining "direct" dependencies, we need to ensure that we respect markers. In the linked issue, the user had an optional dependency like:
By not respecting markers, we tried to resolve
setuptools
to the lowest-available version. However, sincesetuptools>=64
isn't enabled (since it's optional), we won't respect that constraint.To be consistent, we need to omit optional dependencies just as we will at resolution time.
Closes #2203.
Test Plan
cargo test