This release is a pre-release and may not be stable for production use.
1 maintainer
Metadata
1 maintainer
Release files for postling 0.1.0a1
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 | |
|---|---|---|---|---|
| postling-0.1.0a1.tar.gz | 5.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| postling-0.1.0a1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 11.6 kB
Release files / postling-0.1.0a1.tar.gz
| Download URL | postling-0.1.0a1.tar.gz |
|---|---|
| Size | 5.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
31d94dbf27898c318f40a3fadf43ab9ad84d5a39ec78788fc3b58c4e909dc6b3
|
|
BLAKE2b-256 checksum How to use checksums |
da39934b4d80dd4d1b80ed71ce00a81dfe4e770fca2af04d6c2ca14e61415c34
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.12.1
|
Release files / postling-0.1.0a1-py3-none-any.whl
| Download URL | postling-0.1.0a1-py3-none-any.whl |
|---|---|
| Size | 6.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
09f64752a7c1d42d62722ff95418f3896b277159d93f7e4f433b562ae53492e7
|
|
BLAKE2b-256 checksum How to use checksums |
e1839ed6ce64c64074caf88b9a2bc05251f56b40bccdf10f341247c8b00b9900
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.12.1
|
Security for postling 0.1.0a1
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.
