R2C package for pypi
Metadata
Release files for r2c 0.0.1
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 | |
|---|---|---|---|---|
| r2c-0.0.1.tar.gz | 945 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| r2c-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.3 kB
Release files / r2c-0.0.1.tar.gz
| Download URL | r2c-0.0.1.tar.gz |
|---|---|
| Size | 945 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
73aa65bb55b2064c9ea7949d7eabe5be34d9475beaedf8d305d67f0d88e1eba4
|
|
BLAKE2b-256 checksum How to use checksums |
369a3f52499d26142c7e5aba20b77d942b2503a5af8f49a16ef21e7fb1f6dda4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/41.0.1 requests-toolbelt/0.8.0 tqdm/4.29.1 CPython/3.7.2
|
Release files / r2c-0.0.1-py3-none-any.whl
| Download URL | r2c-0.0.1-py3-none-any.whl |
|---|---|
| Size | 1.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d99ce3f78287458aa029875d63ed101eaf748df1f3c6b3bcc139ca844040f213
|
|
BLAKE2b-256 checksum How to use checksums |
24b5a11f9dc54a7fd81c0c411b433d791e090031f198be2cbff13a0d76893bc1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/41.0.1 requests-toolbelt/0.8.0 tqdm/4.29.1 CPython/3.7.2
|
Security for r2c 0.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.