Nodule
Convert, visualize and iterate over heterogeneous trees.
Usage
Usage: nodule [OPTIONS] FORMAT PATH
Convert file at PATH to FORMAT. Supported formats are: JSON, TOML, YAML.
MERMAID is also supported as an output format.
Use `import nodule.nod` to build your own conversion, visualization or
iteration tool.
Options:
--help Show this message and exit.
Out of scope
-
Round trips (X -> X, X -> Y -> X) do not preserve whitespace, comments and layout choices.
-
The built-in Mermaid visualizer may fail with duplicate node names, non-alphanumeric characters and other non-trivial data. Use the
nodifyiterator method to build a robust solution for your use-case. Similarly for smarter and more compact visualizations.
Development environment
Install prerequisites
- Python 3.10
- pdm
- make
- pipx (optional, required for
make install-source)
Instructions
- Fork the upstream repository.
git clone [fork-url]cd [project-folder]- Run
make developto initialise your development environment.
You can use any text editor or IDE that supports virtualenv / pdm. See the Makefile for toolchain details.
Please make test and make lint before submitting changes.
Make targets
USAGE: make [target]
help : Show this message.
develop : Set up Python development environment.
run : Run from source.
clean : Remove all build artefacts.
test : Run tests and generate coverage report.
lint : Fix or warn about linting errors.
build : Clean, test, lint, then generate new build artefacts.
publish : Upload build artefacts to PyPI.
install-source : Install source as a local Python application.
Sharing and contributions
Nodule
https://lofidevops.neocities.org
Copyright 2023 David Seaward and contributors
SPDX-License-Identifier: Apache-2.0
Shared under Apache-2.0. We adhere to the Contributor Covenant 2.1, and certify origin per DCO 1.1 with a signed-off-by line. Contributions under the same terms are welcome.
Submit security and conduct issues as private tickets. Sign commits with
git commit --signoff. For a software bill of materials run reuse spdx. For
more details see CONDUCT, COPYING and CONTRIBUTING.
Metadata
Release files for nodule 0.1.1
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 | Actions |
|---|---|---|---|---|
| nodule-0.1.1.tar.gz | 12.8 kB | Without provenance | Details for nodule-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| nodule-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for nodule-0.1.1-py3-none-any.whl |
Total release size: 36.3 kB
Release files / nodule-0.1.1.tar.gz
| Download URL | nodule-0.1.1.tar.gz |
|---|---|
| Size | 12.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e68784a9b60766e2dd9fbdd65bac99990dc8727aa651a10d7d07c07f9cdde1ef
|
|
BLAKE2b-256 checksum How to use checksums |
6a5fd8f5a4b09add1e3d564d29bb5f0b23ceeb377991825be227b09dd10b30bf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
pdm/2.10.1 CPython/3.10.12
|
Release files / nodule-0.1.1-py3-none-any.whl
| Download URL | nodule-0.1.1-py3-none-any.whl |
|---|---|
| Size | 23.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
be965fd06575208ff1f4e2c1acca3024338a52d0fedb492e81c2afd51d2ca48d
|
|
BLAKE2b-256 checksum How to use checksums |
0a60a0f99d1709a5c9319aa164884750d6236a0570f3c010d1ae2abf785a4b78
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
pdm/2.10.1 CPython/3.10.12
|
Security for nodule 0.1.1
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.