The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for bayesprev 0.1.1
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 | |
|---|---|---|---|---|
| bayesprev-0.1.1.tar.gz | 14.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bayesprev-0.1.1-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 29.4 kB
Release files / bayesprev-0.1.1.tar.gz
| Download URL | bayesprev-0.1.1.tar.gz |
|---|---|
| Size | 14.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b31928047b558771d563adf186240e2bdd223b301c9386dbd2770e75f8fbee86
|
|
BLAKE2b-256 checksum How to use checksums |
8686006983337dbc3b543b9abdbf6d7bddc90c08cbf9c04dd04036174f598219
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-requests/2.26.0
|
Release files / bayesprev-0.1.1-py2.py3-none-any.whl
| Download URL | bayesprev-0.1.1-py2.py3-none-any.whl |
|---|---|
| Size | 15.0 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
697047c378a35a68f89719d8a9bc39997b5f8de7e5ef3f64134f61a397a14603
|
|
BLAKE2b-256 checksum How to use checksums |
370b34232a4e3dfb796eaf2fdf9768442db15127d9bb5ff4c55335008d1a013c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-requests/2.26.0
|
Security for bayesprev 0.1.1
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.
