The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for fancyping 0.3.0
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 | |
|---|---|---|---|---|
| fancyping-0.3.0.tar.gz | 19.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| fancyping-0.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 39.2 kB
Release files / fancyping-0.3.0.tar.gz
| Download URL | fancyping-0.3.0.tar.gz |
|---|---|
| Size | 19.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
04fa9fec9bec56f7653534ef1bf8985688711a9e6a25d6cc6d0b043fa1534f12
|
|
BLAKE2b-256 checksum How to use checksums |
de229c7bdf690dee9a200304918d9c95fade3e8131973e826d838d0a29502085
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.8
|
Release files / fancyping-0.3.0-py3-none-any.whl
| Download URL | fancyping-0.3.0-py3-none-any.whl |
|---|---|
| Size | 19.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
54767720c36261ccee032c1a37d3ba33929c9e5d95ffd5eae08e600b3ad4c911
|
|
BLAKE2b-256 checksum How to use checksums |
7ebb9e07301a3d7672cd40f931ab9dc85442a2f28be72809ecbc77703e0e8d3f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.8
|
Security for fancyping 0.3.0
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.
