Skip to content
Open
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Update docs/references/strategies/languages/python/pipenv.md
Co-authored-by: Jessica Black <[email protected]>
  • Loading branch information
ryanlink and jssblck authored Jan 25, 2024
commit 32b4339b36db9b75071b77d227f29e1cf21ca2cf
5 changes: 1 addition & 4 deletions docs/references/strategies/languages/python/pipenv.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,10 +25,7 @@ dependencies. This will fail unless `pipenv install` has been run in that direct

## Limitations

- Our pipenv strategy currently reports all dependencies as direct. rather than differentiating between direct and transitive.

- Pipfile.lock does not report edges, if `pipenv graph --json-tree` fails, we will
not be able to detect the edges between dependencies.
- This strategy does not report edges between dependencies. This means that all dependencies being used in the project are found, but are all reported as direct dependencies of the project.

- `pipenv graph --json-tree` relies on `pipenv install` being run in the directory beforehand.
If that command was not run (such as in a freshly cloned repo), then the graph command will fail,
Expand Down