Open source Aurelii file format python package by Xonize in OpenDTK
1 maintainer
Metadata
1 maintainer
Release files for aurelii 0.1.2.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 | |
|---|---|---|---|---|
| aurelii-0.1.2.3.tar.gz | 1.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aurelii-0.1.2.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.3 kB
Release files / aurelii-0.1.2.3.tar.gz
| Download URL | aurelii-0.1.2.3.tar.gz |
|---|---|
| Size | 1.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a866295524704c30c439a7458e83f1a12ba76f5843c9fb1d7802dfd2afed04ff
|
|
BLAKE2b-256 checksum How to use checksums |
efb9bdab7de3e2f50e33981230182f8bab81c3ba4a0a8e93d55693b416603126
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.4
|
Release files / aurelii-0.1.2.3-py3-none-any.whl
| Download URL | aurelii-0.1.2.3-py3-none-any.whl |
|---|---|
| Size | 2.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a16679f5ecdd1edf2f3b2ed8b9bb67d5ce0966a57ae8718b470ce0c9a51c2de7
|
|
BLAKE2b-256 checksum How to use checksums |
681ee349a30e79be60b2476979858c70f03afdd53b10004454dd33c2d914474d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.4
|
Security for aurelii 0.1.2.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.
