The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for atmeexpy 0.4.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 | |
|---|---|---|---|---|
| atmeexpy-0.4.0.tar.gz | 6.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| atmeexpy-0.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 11.9 kB
Release files / atmeexpy-0.4.0.tar.gz
| Download URL | atmeexpy-0.4.0.tar.gz |
|---|---|
| Size | 6.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7ccb63f8c350b441dc3bf17f5268c55fd6f1505a95cc0a27de8997c17713ce44
|
|
BLAKE2b-256 checksum How to use checksums |
15b3d81927f2e990fe4e4a02db2ecef007aed56a07998f1322032297d12a859a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Release files / atmeexpy-0.4.0-py3-none-any.whl
| Download URL | atmeexpy-0.4.0-py3-none-any.whl |
|---|---|
| Size | 5.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
920c2db01e593b9b93ddfb0985291cec5591021ce84c69f44d36a93789931c5b
|
|
BLAKE2b-256 checksum How to use checksums |
6db1102c591447bfa167ff0cdae3703918c8b7363034df7e0644cbaff7edc3e6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for atmeexpy 0.4.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.
