2 maintainers
Metadata
2 maintainers
Release files for switching-machine 0.0.2
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 | |
|---|---|---|---|---|
| switching_machine-0.0.2.tar.gz | 8.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| switching_machine-0.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 18.7 kB
Release files / switching_machine-0.0.2.tar.gz
| Download URL | switching_machine-0.0.2.tar.gz |
|---|---|
| Size | 8.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
47147896088da9a9fd6cc6ea042cb3f3b731cb8e524920fe9973863056e9534c
|
|
BLAKE2b-256 checksum How to use checksums |
0663140c066f56cc8a75fd76ecd891bcee6e2599b3ee130270a2ca0934c79c82
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.25
|
Release files / switching_machine-0.0.2-py3-none-any.whl
| Download URL | switching_machine-0.0.2-py3-none-any.whl |
|---|---|
| Size | 10.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fe2e9299288e55373aa282b93b9d966449405adbf8c995ef36094d2b059e3c8f
|
|
BLAKE2b-256 checksum How to use checksums |
4af3563031d7eaf130ac93b3e9e941bc1eb2ddef93b4ae48244a985ac8e276fd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.25
|
Security for switching-machine 0.0.2
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.
