The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for metal-python 0.45.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 | |
|---|---|---|---|---|
| metal_python-0.45.0.tar.gz | 146.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| metal_python-0.45.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 616.9 kB
Release files / metal_python-0.45.0.tar.gz
| Download URL | metal_python-0.45.0.tar.gz |
|---|---|
| Size | 146.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4e62418bbad10aee7b264fd39fa9b39b18e3a1051c2427283969d74a771c6ec2
|
|
BLAKE2b-256 checksum How to use checksums |
0c1985328639c47ded07ef1b12bc8c22fc33523ea7fb3aa0f7229575c79b7d7d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.25
|
Release files / metal_python-0.45.0-py3-none-any.whl
| Download URL | metal_python-0.45.0-py3-none-any.whl |
|---|---|
| Size | 470.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f90f753c5a721a377e75f2e29d4c12f5f7aef06d59815c18ea11ce49bef32ee2
|
|
BLAKE2b-256 checksum How to use checksums |
c8fe46f89b82aedcaba347b8c8bbaf699f97f519e3fd86164749a0fe17b426a4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.25
|
Security for metal-python 0.45.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.
