CFFI bindings to the CMPH library
These bindings provide python with the ability to create and use Minimal Perfect Hashes via the CMPH library.
Installation
Should be as simple as
$ pip install cmph-cffiDevelopment version
The latest development version can be installed directly from GitHub:
$ pip install --upgrade 'git+https://github.com/URXtech/cmph-cffi'Usage
Creating a new MPH
import cmph
with open('/usr/share/dict/words', 'w') as keys:
mph = cmph.generate_hash(keys)Getting keys out of an MPH
mph('Test')Saving the MPH
with open('/tmp/out.mph', 'w') as out_file:
mph.save(out_file)Loading a pre-existing MPH
with open('/tmp/out.mph') as in_file:
cmph.load_hash(in_file)Reporting bugs
Please see BUG_REPORTS.
Contribute
Please see CONTRIBUTING.
Licence
Please see LICENSE.
1 maintainer
Metadata
1 maintainer
Release files for cmph-cffi 0.3.0
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 | Actions |
|---|---|---|---|---|
| cmph-cffi-0.3.0.tar.gz | 82.7 kB | Without provenance | Details for cmph-cffi-0.3.0.tar.gz |
Release files / cmph-cffi-0.3.0.tar.gz
| Download URL | cmph-cffi-0.3.0.tar.gz |
|---|---|
| Size | 82.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0ee85742ed27e17686d8016c210a88c2e638b34e3a8bccbaf348df00419bdccb
|
|
BLAKE2b-256 checksum How to use checksums |
96af2f0f7709d6d0b57ca8db49afca8e7d1cf1463627d889720a8651e5da2796
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for cmph-cffi 0.3.0
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
