The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for rayvision-c4d 1.1.2
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 | |
|---|---|---|---|---|
| rayvision_c4d-1.1.2.tar.gz | 3.3 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| rayvision_c4d-1.1.2-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 3.3 MB
Release files / rayvision_c4d-1.1.2.tar.gz
| Download URL | rayvision_c4d-1.1.2.tar.gz |
|---|---|
| Size | 3.3 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
47eec3f15b1b6c63756ab5d7c63ede02a8f0b52d5a92c00fb9cec0f47a56be18
|
|
BLAKE2b-256 checksum How to use checksums |
d9d9b53dc83d1319809b1220cc51f0b60862478427f819cf478ac9e4d7717b2d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.7.9
|
Release files / rayvision_c4d-1.1.2-py2.py3-none-any.whl
| Download URL | rayvision_c4d-1.1.2-py2.py3-none-any.whl |
|---|---|
| Size | 11.8 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
acaa1435d7920743c0dd2ac43fa2f7e08ef4e211b5ecf8f074cdd13b36e4cfe5
|
|
BLAKE2b-256 checksum How to use checksums |
4984c5f522127ff247d1032eb2f73fa0b6fc047c2aa86c1e2de57ce241395af7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.7.9
|
Security for rayvision-c4d 1.1.2
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.
