disambiguate direct-origin dependencies in show-outdated #6016
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.
if you have, say:
and go
poetry show --outdated
then you hit the runtime errorUnknown direct dependency type None
.The reason is that poetry appears twice, once as a direct dependency and once not. And we happen to search for the direct dependency using the one that isn't, if you see what I mean.
This MR also improves the error message by saying which package is the problematic one.