This release is a pre-release and may not be stable for production use.
pylev2
A Levenshtein implementation with a premissive license. Intended to be a semi-dropin replacement for pylev and to be faster by leveraging a C extension.
Requirements
C compiler
Only tested with Python 2.7
Usage
Simple example.:
import pylev2
distance = pylev2.levenshtein('kittens', 'sitting')
assert(distance, 3)
Changing from pylev to pylev2
Replace all instances of pylev with pylev2, please note that pylev2 does not support the functions with spelling errors or the classic version.
Tests
Setup:
$ virtualenv .env $ .env/bin/pip install git+https://github.com/JohnDoee/pylev2.git
Running:
$ python -m unittest pylev2.tests
License
MIT, see LICENSE
History
Uses semantic versioning
v1.0.0-beta
Initial release.
Metadata
Release files for pylev2 1.0.0-beta
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 |
|---|---|---|---|---|
| pylev2-1.0.0-beta.tar.gz | 3.4 kB | Without provenance | Details for pylev2-1.0.0-beta.tar.gz |
Release files / pylev2-1.0.0-beta.tar.gz
| Download URL | pylev2-1.0.0-beta.tar.gz |
|---|---|
| Size | 3.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
aef7cb3167552cdc15472f7fd8475a71519c79baa9da8389b155dc2172edd991
|
|
BLAKE2b-256 checksum How to use checksums |
98a4cf2b955f0e4180980f376eb7683f275a451e4bcb476700f62f40a9e674fc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for pylev2 1.0.0-beta
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.