Metadata
Release files for experiment_phase_1 0.2.4
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 | |
|---|---|---|---|---|
| experiment_phase_1-0.2.4.tar.gz | 4.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| experiment_phase_1-0.2.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 10.9 kB
Release files / experiment_phase_1-0.2.4.tar.gz
| Download URL | experiment_phase_1-0.2.4.tar.gz |
|---|---|
| Size | 4.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7f9a1897b95169bda1efb6537e9cee2fbaaf3d02dc82752c480c6cc05ae4ac26
|
|
BLAKE2b-256 checksum How to use checksums |
c2c1faadc0edb1f90d520316d15ae2f7edaf5ee27a4241c06e514da484c094e0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.8.3 CPython/3.12.3 Windows/11
|
Release files / experiment_phase_1-0.2.4-py3-none-any.whl
| Download URL | experiment_phase_1-0.2.4-py3-none-any.whl |
|---|---|
| Size | 6.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8ba1d9f34c66773e4a3f532da0f3aed9f4c950dfebfc6570e267db4267c6f5fb
|
|
BLAKE2b-256 checksum How to use checksums |
ce8d8b4b90643a861f1e717550adf7474a3daf68fccc649433beae0570d5e727
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.8.3 CPython/3.12.3 Windows/11
|
Security for experiment_phase_1 0.2.4
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.