Prior to version 0.14.5
hashin would write write down the hashes of PyPI packages in the order they appear in PyPI's JSON response. That means there's a slight chance that two distinct clients/computers/humans might actually get different output when then run
The pull request has a pretty hefty explanation as it demonstrates the fix.
Do note that if the existing order of hashes in a requirements file is not in the "right" order,
hashin won't correct it unless any of the hashes are different.
Thanks @SomberNight for patiently pushing for this.
- How to encrypt a file with Emacs on macOS (ccrypt)
29 January 2019
- Format thousands in Python
01 February 2019
- Related by category:
- How much faster is Redis at storing a blob of JSON compared to PostgreSQL?
28 September 2019
- Best practice with retries with requests
19 April 2017
- Fastest way to find out if a file exists in S3 (with boto3)
16 June 2017
- Interesting float/int casting in Python
25 April 2006
- Fastest way to unzip a zip file in Python
31 January 2018
- Related by keyword:
- "ld: library not found for -lssl" trying to install mysqlclient in Python on macOS
05 February 2020
- Bestest and securest way to handle Python dependencies
01 February 2016
- hashin 0.15.0 now copes nicely with under_scores
15 June 2020
- hashin 0.12.0 is much much faster
20 March 2018
- Concurrent download with hashin without --update-all
18 December 2018