The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for baseball3D 0.1.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 | |
|---|---|---|---|---|
| baseball3D-0.1.3.tar.gz | 12.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| baseball3D-0.1.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 29.8 kB
Release files / baseball3D-0.1.3.tar.gz
| Download URL | baseball3D-0.1.3.tar.gz |
|---|---|
| Size | 12.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
def40a2d8185e5f94d42ddbf08271b14b20ac0541b6edb64492b7bfb574cf936
|
|
BLAKE2b-256 checksum How to use checksums |
e2e8cbc15b3fc0aac47a97785ead39d8d4f652fae6974ef1b0df727b6c54768b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.13
|
Release files / baseball3D-0.1.3-py3-none-any.whl
| Download URL | baseball3D-0.1.3-py3-none-any.whl |
|---|---|
| Size | 17.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
86a3807e6f11a2afccc5d3af9d6ff3e7807d37d4a0fac7e04a42ff1ab615713c
|
|
BLAKE2b-256 checksum How to use checksums |
429ecda35a3959dd23f8aca91cb8d5abd021ac129884d415a9dd44b6f7c5da15
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.13
|
Security for baseball3D 0.1.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.
