The author of this package has not provided a project description
Metadata
Release files for compound-learning 0.0.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 | |
|---|---|---|---|---|
| compound_learning-0.0.1.tar.gz | 485 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| compound_learning-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.6 kB
Release files / compound_learning-0.0.1.tar.gz
| Download URL | compound_learning-0.0.1.tar.gz |
|---|---|
| Size | 485 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4a21c41e18fc9bb86816a7d743c9770ae7bdbde12db8a97c502c78e05e498c0e
|
|
BLAKE2b-256 checksum How to use checksums |
ee7a1c9dca8228eb5ad8bebe2c0179e790797a59c71da52060ef50965013ee72
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.8.2
|
Release files / compound_learning-0.0.1-py3-none-any.whl
| Download URL | compound_learning-0.0.1-py3-none-any.whl |
|---|---|
| Size | 1.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b22e85243a8d4f5e29aaf3baf7e4083e451ce6dbee80d4f98285c7f4abdd472f
|
|
BLAKE2b-256 checksum How to use checksums |
7f08f6d54fb4289198019f59d19ffad0d636acfcf54224e1c713504c5dab2946
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.8.2
|
Security for compound-learning 0.0.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.