Metadata
Release files for RedPy 0.0.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 | |
|---|---|---|---|---|
| RedPy-0.0.3.tar.gz | 2.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| RedPy-0.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.6 kB
Release files / RedPy-0.0.3.tar.gz
| Download URL | RedPy-0.0.3.tar.gz |
|---|---|
| Size | 2.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8b1b6fd59c4a05f27b14ce10a06b3b648763a3e3f3e3840a80ebbf6ca967f421
|
|
BLAKE2b-256 checksum How to use checksums |
5b3e6c61708edb7106ce1f9171287c36f9420371d659d8bea5f11bda3c6c61fe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.4.2 requests/2.21.0 setuptools/40.0.0 requests-toolbelt/0.9.1 tqdm/4.32.1 CPython/3.6.3
|
Release files / RedPy-0.0.3-py3-none-any.whl
| Download URL | RedPy-0.0.3-py3-none-any.whl |
|---|---|
| Size | 2.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
07012dd0188d98b24c27667a91a5fbe0a66f32b12287c68cce077aec4434fe27
|
|
BLAKE2b-256 checksum How to use checksums |
e141cf5f673c08cc63fad4703ab9eb89403f002198af74e0c0b492793d5faf28
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.4.2 requests/2.21.0 setuptools/40.0.0 requests-toolbelt/0.9.1 tqdm/4.32.1 CPython/3.6.3
|
Security for RedPy 0.0.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.