Use regex for dependency version specifier parsing #82
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.
The dependency parsing logic in
generate_dependency_diagram.pyused chainedsplit()calls that failed for dependencies with multiple version specifiers (e.g.,package>=1.0,<2.0).Changes
split('>=')[0].split('==')[0].split('<')[0]with regex-based parsingre.split(r'[><=!~]', dep)[0].strip()to correctly extract package names regardless of version specifier complexity💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.