Metadata
1 maintainer
Release files for texas-hold-em-utils 0.1.17
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 | |
|---|---|---|---|---|
| texas_hold_em_utils-0.1.17.tar.gz | 3.5 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| texas_hold_em_utils-0.1.17-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.7 MB
Release files / texas_hold_em_utils-0.1.17.tar.gz
| Download URL | texas_hold_em_utils-0.1.17.tar.gz |
|---|---|
| Size | 3.5 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
18d21abab9588ad13de539a2a6186e951210e2ac087307b2382e94eb57a86ded
|
|
BLAKE2b-256 checksum How to use checksums |
998856a3c7a5a4db2bb006958698bf8ef018809019bf859c465a58c2aa205f8e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.10.6
|
Release files / texas_hold_em_utils-0.1.17-py3-none-any.whl
| Download URL | texas_hold_em_utils-0.1.17-py3-none-any.whl |
|---|---|
| Size | 1.2 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8247d7c2899b1d2336f59cf05e45e78871e0b6cd6fc0e7013be89a043651a748
|
|
BLAKE2b-256 checksum How to use checksums |
701b1ab5eb48307599ad835244de7a1180be0f33aa4b75b219bf854eb5a09851
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.10.6
|
Security for texas-hold-em-utils 0.1.17
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.
