The author of this package has not provided a project description
Metadata
Release files for blt-trainer 0.1.2
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 | |
|---|---|---|---|---|
| blt_trainer-0.1.2.tar.gz | 8.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| blt_trainer-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 19.5 kB
Release files / blt_trainer-0.1.2.tar.gz
| Download URL | blt_trainer-0.1.2.tar.gz |
|---|---|
| Size | 8.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
315b105494c10d0d5a1d6b55cb2844947eebc9e21505aa1ced8d26cd5eba9752
|
|
BLAKE2b-256 checksum How to use checksums |
561747ecc97815406b786e45bbc6b49534dc51287efaebd0469b52688a2b45f2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.4
|
Release files / blt_trainer-0.1.2-py3-none-any.whl
| Download URL | blt_trainer-0.1.2-py3-none-any.whl |
|---|---|
| Size | 10.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3f4072be7b3a68ac8c20d6651ca041bf197aaa16512d54eb223ccc7b006c40a3
|
|
BLAKE2b-256 checksum How to use checksums |
12630ece3f53e11e7943730ac15bd942233d67db6ef551f29095392617cb6bbe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.4
|
Security for blt-trainer 0.1.2
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.