Release files for moola 0.1.6
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 | |
|---|---|---|---|---|
| moola-0.1.6.tar.gz | 30.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| moola-0.1.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 83.1 kB
Release files / moola-0.1.6.tar.gz
| Download URL | moola-0.1.6.tar.gz |
|---|---|
| Size | 30.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9b5936cef0d2a29432784dea9e4813e3653d5277a66bac67bf5d89ba912ec7ce
|
|
BLAKE2b-256 checksum How to use checksums |
8a592b5ceabeb6f2cdaad4d8f2bdbc2dbcfb459c96144a4859bb985e2939ed1a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.19.1 setuptools/40.4.3 requests-toolbelt/0.8.0 tqdm/4.26.0 CPython/3.5.2
|
Release files / moola-0.1.6-py3-none-any.whl
| Download URL | moola-0.1.6-py3-none-any.whl |
|---|---|
| Size | 52.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
07d3c9582563754309e351dc2e56a72f1cd089f5352fad4cef880f5d400a3f24
|
|
BLAKE2b-256 checksum How to use checksums |
d5ef5763e1973a685bd0b808ad1647f03b08c79aae82314058ec6d7875fa9e15
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.19.1 setuptools/40.4.3 requests-toolbelt/0.8.0 tqdm/4.26.0 CPython/3.5.2
|
Security for moola 0.1.6
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.
