This release is a pre-release and may not be stable for production use.
1 maintainer
Metadata
1 maintainer
Release files for planex2d 0.0.1.dev0
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 | |
|---|---|---|---|---|
| planex2d-0.0.1.dev0.tar.gz | 667 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| planex2d-0.0.1.dev0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.8 kB
Release files / planex2d-0.0.1.dev0.tar.gz
| Download URL | planex2d-0.0.1.dev0.tar.gz |
|---|---|
| Size | 667 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
777ff2847059c927d9e953a2df7cdfe5ca4d5e8f06703bdd861e94d6e658c994
|
|
BLAKE2b-256 checksum How to use checksums |
e3ebe853c110f7cd37133b6e3bce133de0440bde5580dbe30bf4485916f4ac15
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.3
|
Release files / planex2d-0.0.1.dev0-py3-none-any.whl
| Download URL | planex2d-0.0.1.dev0-py3-none-any.whl |
|---|---|
| Size | 1.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3cc51c922fcd13338f25ebb3e4e4a5e0048afd2c55f1012c96ddd9c10e91842c
|
|
BLAKE2b-256 checksum How to use checksums |
38aaa93f7ca33f0bb84ea0cbfb0fae8642e7019a4d43dcc646a1968b6365a306
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.3
|
Security for planex2d 0.0.1.dev0
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.
