The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for assign3-1 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 | |
|---|---|---|---|---|
| assign3_1-0.0.1.tar.gz | 5.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| assign3_1-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.8 kB
Release files / assign3_1-0.0.1.tar.gz
| Download URL | assign3_1-0.0.1.tar.gz |
|---|---|
| Size | 5.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9bf6d51be99941e7000550a7f4109e05b12f4f8f781f9e54058919f7122bb4d3
|
|
BLAKE2b-256 checksum How to use checksums |
b12244d4f00e61341d92c900a891838b03fe442a01ea54eb48dd1be8504ab320
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.6
|
Release files / assign3_1-0.0.1-py3-none-any.whl
| Download URL | assign3_1-0.0.1-py3-none-any.whl |
|---|---|
| Size | 7.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2e6c534695ac14fbea61ffeb54e76037cc1ac1a1f53977832a3aef8d41f4ed9c
|
|
BLAKE2b-256 checksum How to use checksums |
f7b572af563be1b1a53c8861bab599da2b51a8a922607f1a5d5d6f5563b2fbf7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.6
|
Security for assign3-1 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.
