The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for dayan-sync 1.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 | |
|---|---|---|---|---|
| dayan_sync-1.0.tar.gz | 43.7 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dayan_sync-1.0-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 87.5 MB
Release files / dayan_sync-1.0.tar.gz
| Download URL | dayan_sync-1.0.tar.gz |
|---|---|
| Size | 43.7 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
94d3920c3d9614efd01c99f2291582776ef2bc8a7b7d7024336d61ee831092ae
|
|
BLAKE2b-256 checksum How to use checksums |
605e897e06f766be5628525238b46a6d682648f63ae33159a2dc69a80b3a1b64
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.7.0
|
Release files / dayan_sync-1.0-py2.py3-none-any.whl
| Download URL | dayan_sync-1.0-py2.py3-none-any.whl |
|---|---|
| Size | 43.8 MB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
a9f806159e7ac37e270477dc63c379e99a25344c159b339f202178af88b83433
|
|
BLAKE2b-256 checksum How to use checksums |
628bd32199bff3421538263168cf7b1256b0ee86eddb764eb4dee1353ce4f495
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.7.0
|
Security for dayan-sync 1.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.
