This is an demo python package created by me. Once we know how to create a python package will apply the same steps for client librarary.
1 maintainer
Metadata
1 maintainer
Release files for MyPythonPkg 0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| MyPythonPkg-0.1-py3-none-any.whl | Python 3 | none | any | Details |
Release files / MyPythonPkg-0.1-py3-none-any.whl
| Download URL | MyPythonPkg-0.1-py3-none-any.whl |
|---|---|
| Size | 1.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a97ce85147f2d73a840d508d6b0a3e7416c044dad4dc70493a8c836e329a2cb9
|
|
BLAKE2b-256 checksum How to use checksums |
8a06c2f16f8524a2146f5702cb9e40b51cb648a39a1b05f5ce138d5a0b8a12b9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/2.0.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.6.0 requests-toolbelt/0.9.1 tqdm/4.38.0 CPython/3.7.3
|
Security for MyPythonPkg 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.
