Skip to content
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

ignore current hashes using --no-reuse-hashes #1176

Closed
graingert opened this issue Jul 9, 2020 · 1 comment · Fixed by #1177
Closed

ignore current hashes using --no-reuse-hashes #1176

graingert opened this issue Jul 9, 2020 · 1 comment · Fixed by #1177
Labels
cli Related to command line interface things enhancement Improvements to functionality hashes Related to hashes generated via --generate-hashes

Comments

@graingert
Copy link
Member

graingert commented Jul 9, 2020

it might be worth always getting the hashes now rather than skipping them if the hashes are already in the requirements.txt (this behaviour causes me problems, eg when new wheels are uploaded to an old version I don't get the hash of the new wheel)

We could ignore current hashes using --rebuild. What do you think?

Originally posted by @atugushev in #1109 (comment)

see also https://github.com/jazzband/pip-tools/pull/641/files

@graingert graingert changed the title ignore current hashes using --rebuild ignore current hashes using --no-reuse-hashes Jul 9, 2020
graingert added a commit to graingert/pip-tools that referenced this issue Jul 9, 2020
@graingert
Copy link
Member Author

#1177

@atugushev atugushev added enhancement Improvements to functionality cli Related to command line interface things labels Jul 18, 2020
@atugushev atugushev added the hashes Related to hashes generated via --generate-hashes label Jul 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cli Related to command line interface things enhancement Improvements to functionality hashes Related to hashes generated via --generate-hashes
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants