The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for bartpy2 0.0.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 | |
|---|---|---|---|---|
| bartpy2-0.0.2.tar.gz | 21.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bartpy2-0.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 45.9 kB
Release files / bartpy2-0.0.2.tar.gz
| Download URL | bartpy2-0.0.2.tar.gz |
|---|---|
| Size | 21.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a65f10ccd838c8ced17449172d0a277885fa6dc3d0ed267731e20d41cdb44f6c
|
|
BLAKE2b-256 checksum How to use checksums |
0278e1fd67f411083e9c54953f2053b629f27d8b279b9211abc82a451fdde84f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.2
|
Release files / bartpy2-0.0.2-py3-none-any.whl
| Download URL | bartpy2-0.0.2-py3-none-any.whl |
|---|---|
| Size | 24.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b7cd603005031b2a9a71e82c86f7e6a4c9bd4d67d249619d58f57cbe3d139fa2
|
|
BLAKE2b-256 checksum How to use checksums |
ae9219ecee4620f8b5e5f64463e345e3c88cf1d8b7201a025ba86d3425a4da19
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.2
|
Security for bartpy2 0.0.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.
