This release is a pre-release and may not be stable for production use.
1 maintainer
Metadata
1 maintainer
Release files for thedus 0.2.0b0
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 | |
|---|---|---|---|---|
| thedus-0.2.0b0.tar.gz | 11.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| thedus-0.2.0b0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 20.5 kB
Release files / thedus-0.2.0b0.tar.gz
| Download URL | thedus-0.2.0b0.tar.gz |
|---|---|
| Size | 11.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dcf21a7b0e0e23575bab07dc2c1d4544b6876b420a8ec2e4fd3712330712580c
|
|
BLAKE2b-256 checksum How to use checksums |
603feb86bc0e996f172e0eaec0efb0101f232a220a24376ce41c056a94d6468f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Release files / thedus-0.2.0b0-py3-none-any.whl
| Download URL | thedus-0.2.0b0-py3-none-any.whl |
|---|---|
| Size | 9.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3173f444e2ae797c38bd4c885beab29507d8847df9898dc1d9199322ad7a8774
|
|
BLAKE2b-256 checksum How to use checksums |
6f9e24a7c87461e290ee9c4429770fa58e34c49eb1494da2d503cecb4d51fbd7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Security for thedus 0.2.0b0
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.
