The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for kemlglearn 0.4.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 | |
|---|---|---|---|---|
| kemlglearn-0.4.3.tar.gz | 34.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| kemlglearn-0.4.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 84.5 kB
Release files / kemlglearn-0.4.3.tar.gz
| Download URL | kemlglearn-0.4.3.tar.gz |
|---|---|
| Size | 34.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d07137ba0842561eb06d10abe93c1906d988266242ef76d5d2b6bbe0e896ed77
|
|
BLAKE2b-256 checksum How to use checksums |
f514ce55d4f44ecef92d366d325a467c523c27075a14f035189d32cb73848c0c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.11
|
Release files / kemlglearn-0.4.3-py3-none-any.whl
| Download URL | kemlglearn-0.4.3-py3-none-any.whl |
|---|---|
| Size | 50.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a95a87e5faf23e1737ceb291b8086b52ade91bc913555c1d650490fc2578fd62
|
|
BLAKE2b-256 checksum How to use checksums |
463315b187063b084c87bbc21f45ce55deac7ba244fb4667cd87de3e347ef641
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.11
|
Security for kemlglearn 0.4.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.
