Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Use `pip`'s new `--dry-run` and `--report` flags

See original GitHub issue

On sufficiently new pip versions (not yet released), these flags will allow us to punt all dependency resolution directly to pip and retrieve a corresponding JSON report.

pip-audit should detect and support these versions of pip, leveraging their “official” dependency resolution flow rather than our internal one.

See https://github.com/pypa/pip/pull/10771.

Issue Analytics

State:
Created a year ago
Reactions:1
Comments:8 (8 by maintainers)

Top GitHub Comments

1reaction

dicommented, Jul 21, 2022

Reminder that the goal of pip-audit is to be a drop-in replacement for pip’s internal APIs. So whatever the function/API is that pip uses internally is what we should mimic in pip-api… I haven’t looked but this is probably some type of install function instead.

0reactions

dicommented, Jul 25, 2022

Thanks @pradyunsg! Since the ultimate goal of pip-api is to get people to stop using pip’s internal API by providing an equivalent API that wraps the CLI instead, it’s important for pip-api to mimic that as much as possible.

Also, when integrating into pip, being able to easily replace calls to pip-api with calls from within pip should make integration easier – but if I’m missing something, definitely let me know.