We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Let's say I want to ensure the hashes for a package I've found are the ones I've decided on.
I could have a req.in file like this:
req.in
flymetothemoon==1.4.1 --hash=sha256:e9c771b6136f2392f5c1ca2c8045d0e503981f8c90a111213473e4644765df4f
pip-compile will ignore the provided hash(es), and fetch/generate new ones with the --generate-hashes option.
pip-compile
--generate-hashes
--hash
Being able to provide hashes explicitly is useful if I'm computing them myself.
The text was updated successfully, but these errors were encountered:
Just out of the curiosity, what's the use case for this feature in the wild?
Sorry, something went wrong.
No branches or pull requests
What's the problem this feature will solve?
Let's say I want to ensure the hashes for a package I've found are the ones I've decided on.
I could have a
req.in
file like this:pip-compile
will ignore the provided hash(es), and fetch/generate new ones with the--generate-hashes
option.Describe the solution you'd like
--generate-hashes
is implied if--hash
appears for any package.Being able to provide hashes explicitly is useful if I'm computing them myself.
The text was updated successfully, but these errors were encountered: