SystemRDL to NaturalDocs
[[TOC]]
Description
It generates registers memory map documentation from SystemRDL input files to NaturalDocs output.
1 maintainer
Metadata
1 maintainer
Release files for rdl2nd 0.1.0
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 | |
|---|---|---|---|---|
| rdl2nd-0.1.0.tar.gz | 5.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| rdl2nd-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.8 kB
Release files / rdl2nd-0.1.0.tar.gz
| Download URL | rdl2nd-0.1.0.tar.gz |
|---|---|
| Size | 5.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a0a6ed39ba18c2d69334bd3edac07bc757f7a7ee43582a47f39abb9fbe76734e
|
|
BLAKE2b-256 checksum How to use checksums |
f8e0c7399d595ceaebef0e6ef5e419817bcd8413bf43722950461f58e02e2ed0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.1
|
Release files / rdl2nd-0.1.0-py3-none-any.whl
| Download URL | rdl2nd-0.1.0-py3-none-any.whl |
|---|---|
| Size | 6.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8123db633143462d8bd2bbd64e12e5468dbf26cba8a672b45a72f161dbf26914
|
|
BLAKE2b-256 checksum How to use checksums |
d3f3b5a8892c0f656484cc791165cf7b5ccc38a7e1ac8a23a20c82c859f1a581
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.1
|
Security for rdl2nd 0.1.0
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.
