🐛 fix(cli): show full dependency chain in missing deps error#1019
Merged
gaborbernat merged 2 commits intomainfrom Apr 9, 2026
Merged
🐛 fix(cli): show full dependency chain in missing deps error#1019gaborbernat merged 2 commits intomainfrom
gaborbernat merged 2 commits intomainfrom
Conversation
The dependency chain was split across two lines: the top-level package appeared standalone (suggesting it was missing), followed by the transitive chain on a separate line. Now the full chain displays as a single line (e.g. "pyvex -> bitstring -> bitarray"). Fixes #875
henryiii
approved these changes
Apr 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
When running
--no-isolationbuilds with unsatisfied transitive dependencies, the error message was misleading. 🐛 A chain likepyvex>=9.2.123 -> bitstring -> bitarray<3.1was split across two lines:pyvex>=9.2.123appeared standalone (as if missing itself), thenbitstring -> bitarray<3.1,>=3.0.0on a separate line. Users spent significant time debugging because the output suggested the top-level package was the problem.The formatting logic now renders each unmet dependency as a single line showing the full chain from the declared build dependency down to the actual unsatisfied requirement. A direct missing dependency still shows as a single name, while transitive failures display as
parent -> child -> failing_dep.Fixes #875