1 maintainer
Metadata
1 maintainer
Release files for trie-memoize 0.1.1
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 | |
|---|---|---|---|---|
| trie-memoize-0.1.1.tar.gz | 2.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| trie_memoize-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 6.5 kB
Release files / trie-memoize-0.1.1.tar.gz
| Download URL | trie-memoize-0.1.1.tar.gz |
|---|---|
| Size | 2.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b5651fe6900fcede24d6e829e2f5228250bd4f2e6f238af967d11a6067401ea2
|
|
BLAKE2b-256 checksum How to use checksums |
76263e274a2a078d7c7a7d5da3ffc0a76f03f5421aadf6c701394694130a3d41
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.0.0a2 CPython/3.7.2 Darwin/18.2.0
|
Release files / trie_memoize-0.1.1-py3-none-any.whl
| Download URL | trie_memoize-0.1.1-py3-none-any.whl |
|---|---|
| Size | 4.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3054f23638b9325e3fbc8b5955b327b4160ce6e55c626a3ef25f10ed93e2b99b
|
|
BLAKE2b-256 checksum How to use checksums |
cb6b4db22950911dbe0174a60cba628dbdf0cda38afbb7d301468c48c6076daa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.0.0a2 CPython/3.7.2 Darwin/18.2.0
|
Security for trie-memoize 0.1.1
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.
