The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for pimpmyplot 0.0.6
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 | |
|---|---|---|---|---|
| pimpmyplot-0.0.6.tar.gz | 5.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pimpmyplot-0.0.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 10.6 kB
Release files / pimpmyplot-0.0.6.tar.gz
| Download URL | pimpmyplot-0.0.6.tar.gz |
|---|---|
| Size | 5.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f29f8fbbd2fd19fa70be8cff3e2376e88ed44178c1944bdd1b6babc2b42ef53f
|
|
BLAKE2b-256 checksum How to use checksums |
81df9f32f2449d8a25f09aee9439de8e07740422e735f9d4ff1d6c9d002a0424
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.9
|
Release files / pimpmyplot-0.0.6-py3-none-any.whl
| Download URL | pimpmyplot-0.0.6-py3-none-any.whl |
|---|---|
| Size | 5.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7e05e1f879e5197a2c075de8d4cb0990a3d93af8a2ee7e107816e526cf126105
|
|
BLAKE2b-256 checksum How to use checksums |
b5700c624ba533f00a1fc00cd9ccc568bf002ba96f2b46a6cc2d0f96f68e6808
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.9
|
Security for pimpmyplot 0.0.6
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.
