SimString Python Package
Orginal version by chokkan, available here. New version (compiles under macOS) from here.
Windows/Anaconda/VisualStudio specific steps:
Make sure that iconv is available to your desired conda environment: conda install -c conda-forge libiconv
Then, open a Visual Studio Developer Prompt (e.g. “VS 2015 x64 Developer Command Prompt” or “VS 2015 x86 Developer Command Prompt”)
Now you can any of these commands to build or install:
python setup.py build
python setup.py install
NOTE: If there is a failure that ‘rc.exe’ cannot be found, add the appropriate WindowKits binary path to PATH. More info on this here.
Metadata
Release files for quickumls-simstring 1.1.5r1
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 |
|---|---|---|---|---|
| quickumls_simstring-1.1.5r1.tar.gz | 68.5 kB | Without provenance | Details for quickumls_simstring-1.1.5r1.tar.gz |
Release files / quickumls_simstring-1.1.5r1.tar.gz
| Download URL | quickumls_simstring-1.1.5r1.tar.gz |
|---|---|
| Size | 68.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e6c6d8ace730ef3d703e2e479694914e544762ee5d37e26536b95001b426666b
|
|
BLAKE2b-256 checksum How to use checksums |
0f1b3ff664369b713936a0f9282cbbd8ce7289f0b14d34971250a504485684a3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.32.1 CPython/3.6.8
|
Security for quickumls-simstring 1.1.5r1
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.