heulistic-axolotl
Axolotl config schema and validation, as a small dependency-light Python package.
It is the shared core behind heulistic validate-config in the CLI and config
validation in the Heulistic API, so both agree on what a valid Axolotl config
looks like.
What it gives you
The schema is generated from Axolotl's own config reference, not hand-written, so it knows every field's type, whether it is required, its default, and its documentation — 390 top-level fields and 23 nested models at present.
from heulistic_axolotl.schema import get_field, is_known_field
get_field("micro_batch_size").type.accepts(4) # True
get_field("micro_batch_size").type.accepts(True) # False — bool is not an int
get_field("bf16").type.accepts("auto") # True — Literal['auto'] | bool
get_field("learning_rate").required # True
get_field("sample_packing").doc # the upstream doc comment
is_known_field("lr") # False — it's `learning_rate`
Refreshing for a new Axolotl release
-
Replace
reference/axolotl.yamlwith the current config reference. -
Regenerate the schema:
python -m heulistic_axolotl.generate
-
Run the tests:
pytest
tests/test_real_reference.py holds field counts as tripwires, so a refresh
that changes the schema fails loudly and the diff of _schema_data.py shows
exactly which fields were added, removed, or retyped. Update the constants once
the change is confirmed against the Axolotl changelog.
Layout
| Path | Role |
|---|---|
reference/axolotl.yaml |
Upstream reference, verbatim. Dev input; not shipped in the wheel. |
src/heulistic_axolotl/_reference.py |
Parser for the reference format. Build-time only. |
src/heulistic_axolotl/generate.py |
Writes _schema_data.py. Run by hand. |
src/heulistic_axolotl/_schema_data.py |
Generated. Committed so schema changes are reviewable. |
src/heulistic_axolotl/schema.py |
The runtime API — SCHEMA, get_field, get_model. |
src/heulistic_axolotl/spec.py |
Field, TypeExpr, and type-expression parsing. |
Licence
MIT.
Metadata
Release files for heulistic-axolotl 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 | |
|---|---|---|---|
| heulistic_axolotl-0.1.0.tar.gz | 52.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| heulistic_axolotl-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 97.1 kB
Release files / heulistic_axolotl-0.1.0.tar.gz
| Download URL | heulistic_axolotl-0.1.0.tar.gz |
|---|---|
| Size | 52.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
40f1235ea85d10c40c2b30f6a5c23373c749bb811ec73e8622f20855b5589e25
|
|
BLAKE2b-256 checksum How to use checksums |
cd8efb35dae86f1c400fc8ff7c4cdedca0422b25e0f0619534157cc7a5e3d44e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 30, 2026.
Transparency logRelease files / heulistic_axolotl-0.1.0-py3-none-any.whl
| Download URL | heulistic_axolotl-0.1.0-py3-none-any.whl |
|---|---|
| Size | 44.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a16bc817427f9a0795c7e8b76668b973c7cba7fd3385fb6f26899acc1be283ad
|
|
BLAKE2b-256 checksum How to use checksums |
fbf0924cb56870e261596ef980858d814a5d713c31c95850a801813c7c88f4a2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 30, 2026.
Transparency log