The author of this package has not provided a project description
Metadata
Release files for rayvision-sync 3.1.8
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_sync-3.1.8.tar.gz | 43.7 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| rayvision_sync-3.1.8-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 87.5 MB
Release files / rayvision_sync-3.1.8.tar.gz
| Download URL | rayvision_sync-3.1.8.tar.gz |
|---|---|
| Size | 43.7 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d6bbb4dc6ce217bb38a46cadfdffaabae76fe71341a1b0168fa276d25aadd446
|
|
BLAKE2b-256 checksum How to use checksums |
5295824590dd1610f7a60cf0a943db106e2f7cde09fda6054323f5ae824029ad
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.7.9
|
Release files / rayvision_sync-3.1.8-py2.py3-none-any.whl
| Download URL | rayvision_sync-3.1.8-py2.py3-none-any.whl |
|---|---|
| Size | 43.8 MB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
3a2611cbc68c7634fe2b37096ad1371dea0cc4ad502fc141a252e7e073c137ad
|
|
BLAKE2b-256 checksum How to use checksums |
c11a36d5410f10b0b4cd76b446a6d6758ffa647460691d5de4ac127b4df4f6b3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.7.9
|
Security for rayvision-sync 3.1.8
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.