2 maintainers
Metadata
2 maintainers
Release files for iris-datalake-module 0.0.0
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 | |
|---|---|---|---|---|
| iris_datalake_module-0.0.0.tar.gz | 756 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| iris_datalake_module-0.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.2 kB
Release files / iris_datalake_module-0.0.0.tar.gz
| Download URL | iris_datalake_module-0.0.0.tar.gz |
|---|---|
| Size | 756 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
214444baa5fa1268bb6871b9ec9470015406eeef7fa1d508dffb7afa9507c8e1
|
|
BLAKE2b-256 checksum How to use checksums |
1bdcb7780fec7e9df0c73f4237a846db57932014abd7b4a9f3c1aed7fe5ec83d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Release files / iris_datalake_module-0.0.0-py3-none-any.whl
| Download URL | iris_datalake_module-0.0.0-py3-none-any.whl |
|---|---|
| Size | 1.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
501e2e59bf86fd53f1ae6778e9f9616741c5300e773ce5f6dc509771c926dd86
|
|
BLAKE2b-256 checksum How to use checksums |
7757600cf2f069c62a9c942317aafaa6b94c31c27199e141a28ff229b0f33139
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Security for iris-datalake-module 0.0.0
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.
