This is my sumbission for the Assignment 10 in CS 501 Advanced Systems Programming.
1 maintainer
Metadata
1 maintainer
Release files for assin10 0.1.3
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 | |
|---|---|---|---|---|
| assin10-0.1.3.tar.gz | 2.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| assin10-0.1.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.6 kB
Release files / assin10-0.1.3.tar.gz
| Download URL | assin10-0.1.3.tar.gz |
|---|---|
| Size | 2.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a992143b8dfa50c213443f4ebb7ac4417626a1a5e6484ae5f7b233eb90018776
|
|
BLAKE2b-256 checksum How to use checksums |
7b627263596e5d9287afefc494e2d8d7d8d28f601524be42c918fcb2564732cd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.13
|
Release files / assin10-0.1.3-py3-none-any.whl
| Download URL | assin10-0.1.3-py3-none-any.whl |
|---|---|
| Size | 2.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e1e34c9eaaae7bf5eaf43305d0660f46d42b4b6c8c77e1034af63e27bbc4ef48
|
|
BLAKE2b-256 checksum How to use checksums |
9554ad0e63f9624583180ca4f82123a906ce957d747800b98c7f4a7e0246869c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.13
|
Security for assin10 0.1.3
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.
