-
Notifications
You must be signed in to change notification settings - Fork 343
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow lockfile to be read from STDIN #95
Comments
fwiw supporting this "natively" (i.e. without writing a temp file to disk) would require a refactor of the whole Personally I think using a temp file is the way to go (at least for now) because while arguably that defeats the point of using a pipe, the scanner can't actually take advantage of the file contents being streamed anyway in most cases (and I doubt it'd ever be able to) - you should be able to archive that in userland right now by doing:
(of course #94 will make that easier) Having said that, I think it's reasonable for the scanner to support sorting out the temp file when you give it |
Somewhat related, I'd love to see external I could use a similar temporary file path solution, but that doesn't seem ideal. |
@picatz could you create a new issue for that, as it can be actioned separately - the reason why I originally wrote the parsers to take a string is that they use one of ~3 methods for reading the file, not all of which I think just take an My ideal state would be having the parsers in their current form/func name take |
Thank you for the quick response @G-Rath, happy to make an issue! |
It would be helpful to read the lockfile from STDIN. For the Python use case, that would enable something like this:
By allowing pip to identify the transitive dependencies, I get a more complete scan.
I would expect that this enhancement would be stuck behind #94, as STDIN removes the naming hints for the lockfile type.
The text was updated successfully, but these errors were encountered: