The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for yessql 0.2.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 | |
|---|---|---|---|---|
| yessql-0.2.3.tar.gz | 19.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| yessql-0.2.3-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 41.6 kB
Release files / yessql-0.2.3.tar.gz
| Download URL | yessql-0.2.3.tar.gz |
|---|---|
| Size | 19.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d3414b2527d6691cf469daffbced94cc055f9bacb8ce225b2468be3ce18184fe
|
|
BLAKE2b-256 checksum How to use checksums |
dfdad7a9c5a3b5816d539063b5873a8524c03cc4a2abe08435bdfa1227e9852d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.1
|
Release files / yessql-0.2.3-py2.py3-none-any.whl
| Download URL | yessql-0.2.3-py2.py3-none-any.whl |
|---|---|
| Size | 21.8 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
7e55829fd0437898d6458587c5e600c0bac87a0653fe357859e17698c6b6eaba
|
|
BLAKE2b-256 checksum How to use checksums |
efac2f0becd2c65d83daa6f0f4d1bba09891bf856f5aec7c2ca483eaf8c6420f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.1
|
Security for yessql 0.2.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.
