Merge hash function from crc32 and lookup
c version by jingmi , python wrapper by zsp:
from clhash import get_unsigned_hash,get_hash
print get_unsigned_hash(“stdyun.com zsp007@gmail.com”)
print get_hash(“stdyun.com zsp007@gmail.com”)
Reference: http://burtleburtle.net/bob/hash/doobs.html
Metadata
Release files for clhash 1.002
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| clhash-1.002.tar.gz | 4.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| clhash-1.002.win32-py2.6.exe | Details |
Total release size: 207.0 kB
Release files / clhash-1.002.tar.gz
| Download URL | clhash-1.002.tar.gz |
|---|---|
| Size | 4.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6e62fecbda35c1ff5397aae389d2bd3cd5282b707dec61d8e970ba7755a6f063
|
|
BLAKE2b-256 checksum How to use checksums |
a9957b7e7b010efccc60ed9582d647e549d4b46b64c1ffde57c096cb4afb3378
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / clhash-1.002.win32-py2.6.exe
| Download URL | clhash-1.002.win32-py2.6.exe |
|---|---|
| Size | 202.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
29ff3616bf26a987fdbeca9d6748e5ff91e76f8a2361892d51f9dad185c2028f
|
|
BLAKE2b-256 checksum How to use checksums |
1eec71dcdc1c3b6524e56afe6b853a947ec83b2fdcaf97fbba78365680583beb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for clhash 1.002
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.