dizzy.generators.paths¶
dizzy.generators.paths
¶
Output-path helpers for the lib/-only layout.
Generated python code (gen_def / gen_int) and the per-element packages all
live under lib/python-uv/ so each runtime tree is self-contained. gen_def and
gen_int are installable uv packages: their project directory (the one holding
pyproject.toml) wraps an importable package directory of the same name, so the
import names gen_def / gen_int used throughout the generated code keep working.
lib_python_uv_dir(output_dir)
¶
The python-uv runtime workspace root (holds the workspace pyproject.toml).
Source code in dizzy/src/dizzy/generators/paths.py
13 14 15 | |
gen_def_pkg_dir(output_dir)
¶
gen_def project directory — holds its pyproject.toml.
Source code in dizzy/src/dizzy/generators/paths.py
18 19 20 | |
gen_def_root(output_dir)
¶
Importable gen_def package root (.../gen_def/gen_def).
Source code in dizzy/src/dizzy/generators/paths.py
23 24 25 | |
gen_int_pkg_dir(output_dir)
¶
gen_int project directory — holds its pyproject.toml.
Source code in dizzy/src/dizzy/generators/paths.py
28 29 30 | |
gen_int_root(output_dir)
¶
Importable gen_int package root (.../gen_int/gen_int).
Source code in dizzy/src/dizzy/generators/paths.py
33 34 35 | |
gen_schema_root(output_dir, subdir=DEFAULT_JSON_SCHEMA_DIR)
¶
Root for runtime-neutral generated contracts (JSON Schema).
Deliberately a sibling of def/ and lib/ rather than a child of
lib/python-uv/: JSON Schema is consumed by every runtime — and by things that
are not a runtime at all, like an HTTP edge or a docs site — so parking it inside
one language tree would misfile it. The gen_ prefix keeps it recognisable as
generated, alongside gen_def / gen_int.
Source code in dizzy/src/dizzy/generators/paths.py
41 42 43 44 45 46 47 48 49 50 | |