ExpEYES17 PIP Package
entry points : none. This is only a library
maintainer : Jithin B P jithinbp@gmail.com
from eyes17.eyes import *
Metadata
Release files for eyes17lib 2.0.4
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 | |
|---|---|---|---|---|
| eyes17lib-2.0.4.tar.gz | 101.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| eyes17lib-2.0.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 222.9 kB
Release files / eyes17lib-2.0.4.tar.gz
| Download URL | eyes17lib-2.0.4.tar.gz |
|---|---|
| Size | 101.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f61da5e22c2cb61fa245acc4d3799777e30952b0acc172df61de2b681531933c
|
|
BLAKE2b-256 checksum How to use checksums |
d068ea5c7b23ebe28eff43c961f92f471c083f18d32abcfa8e287c2d3fec877a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.12.3
|
Release files / eyes17lib-2.0.4-py3-none-any.whl
| Download URL | eyes17lib-2.0.4-py3-none-any.whl |
|---|---|
| Size | 121.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
58f0615b5498ee1c6e5d8bcb438e33dbc12edae2c839936d6aad5af9f2efdea2
|
|
BLAKE2b-256 checksum How to use checksums |
b4cc1a734806e6015263984e08c5901da42390b49382ade685a2e2fae0c27f14
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.12.3
|
Security for eyes17lib 2.0.4
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.