The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for dspy-kya 0.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 | |
|---|---|---|---|---|
| dspy_kya-0.1.0.tar.gz | 9.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dspy_kya-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 18.8 kB
Release files / dspy_kya-0.1.0.tar.gz
| Download URL | dspy_kya-0.1.0.tar.gz |
|---|---|
| Size | 9.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1163626503fa5e765c48208ac06acda5e5f799b3873b9f699e95f1305e9b9b41
|
|
BLAKE2b-256 checksum How to use checksums |
b1bcb5e70885a994f03bbe6f55f25fef169589845b5ec95d61d2843ac92f9729
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.2
|
Release files / dspy_kya-0.1.0-py3-none-any.whl
| Download URL | dspy_kya-0.1.0-py3-none-any.whl |
|---|---|
| Size | 9.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dae7d272e650999a7909c03b245993224184e3552e928db4d3e0b338d93deffd
|
|
BLAKE2b-256 checksum How to use checksums |
f182e7ecfad6b9d99a94d602d14c0923d15bb114644d8e6ef765e2a87557f292
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.2
|
Security for dspy-kya 0.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.
