Match against requirements.txt and print only those deps that are new

[nfx]

It's very common scenario to discover "what new dependencies do we need to create RPM for" and it'll be super helpful for this tooling to match against an existing requirements.txt file.

[wimglenn]

Hi nfx, I don't understand the request. Could you provide an example input and expected output?

[paultop6]

I think what nfx is after (and I also) is to be able to get the full dependency tree for all packages defined in a given requirements.txt file.

[nfx]

@wimglenn imagine someone works in an environment, where every package is explicitly built, checked for CVE flaws, and copied into local PyPI clone or RPM/DEB repo. And once in a while someone comes and asks "Hey, can we install package X and Y?", without actual knowledge that they need 20-30 transitive dependency packages. this tool can help with that.

[gforcada]

tools like pip-tools pip-compile might help here? 🤔 you store only the top-level requirements on a requirements.in and pip-compile resolves all dependencies generating a so-called lock-file ✨ I'm a huge fan of it 🤩