Consider all Python packages as direct dependencies #408
Conversation
This file contains 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
talarian1
added
the
safe to test
asafgabai
suggested changes
Aug 27, 2023
talarian1
force-pushed
the
fix-python-ca
branch
from
17a671e
to
587c2b9
Compare
talarian1
added
safe to test
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
As a result of the way Python packages are consumed by Python projects, we can't confidently say if a package is a direct dependency of the current project. It was decided that is more accurate to treat all Python dependencies as direct dependencies and include them all in the Contextual Analysis scan.
Please notice that the
Populate each node's childrensection is still needed for the impact graph display: