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

Add option to specify preference of archive formats #3622

Closed
Kentzo opened this issue Apr 23, 2016 · 1 comment
Closed

Add option to specify preference of archive formats #3622

Kentzo opened this issue Apr 23, 2016 · 1 comment
Labels
auto-locked Outdated issues that have been locked by automation

Comments

@Kentzo
Copy link

Kentzo commented Apr 23, 2016

  • Pip version: 8.1.1
  • Python version: 3.5
  • Operating System: Ubuntu 14.04

Description:

The --hash and --require-hashes options allow to validate archive that was downloaded from PyPI. However, if package is available in multiple formats the validation will fail because pip may pick different format than was used to calculate hash.

robin0371 added a commit to robin0371/pip that referenced this issue Apr 30, 2016
…ackage is available in multiple formats.
robin0371 added a commit to robin0371/pip that referenced this issue Apr 30, 2016
robin0371 added a commit to robin0371/pip that referenced this issue Apr 30, 2016
…ulate hash if package is available in multiple formats.
robin0371 added a commit to robin0371/pip that referenced this issue Apr 30, 2016
robin0371 added a commit to robin0371/pip that referenced this issue Apr 30, 2016
robin0371 added a commit to robin0371/pip that referenced this issue Apr 30, 2016
@dstufft
Copy link
Member

dstufft commented Sep 7, 2016

Instead of this I think this would be better solved by #3634 which would enable pip to select files based off of the hashes that it has rather than making a special cased solution just for archive formats.

@dstufft dstufft closed this as completed Sep 7, 2016
@lock lock bot added the auto-locked Outdated issues that have been locked by automation label Jun 4, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jun 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
auto-locked Outdated issues that have been locked by automation
Projects
None yet
Development

No branches or pull requests

2 participants