stapel-attributes
Typed attributes engine: an L1 library (no models, migrations, views, urls, comm surface or service identity of its own) providing a polymorphic type-plugin system (config/dto/dao/type per feature type) behind an open registry, thirteen built-in types (two of them vocabulary-backed, one composite), a closed conditional-rule grammar shared with the TypeScript evaluator, DTO/DAO validation and normalization, polymorphic DRF serializers with OpenAPI schemas, and a schema-driven (Lit 3) admin config editor. Imported directly by stapel-categories (feature schema) and stapel-listings (value validation).
Part of the Stapel framework — composable Django apps that deploy as a monolith or as microservices without changing module code.
Install
pip install stapel-attributes
At a glance
| Fact | Value |
|---|---|
| Version | 0.9.4 |
| Python | >=3.11 (3.11, 3.12, 3.13, 3.14) |
| Django | djangorestframework>=3.14 |
| Config axes | 1 |
| Usage surface | 59 |
| Extension points | 5 |
| Error codes | 55 |
| Fleet dependencies | stapel-core |
Documentation
capabilities.json · llms.txt (for agents)
What this is
This is an L1 library, not a module: it ships no models, migrations,
views, urls or comm surface. Both stapel-categories (attribute schema) and
stapel-listings (attribute values) import it — the code both need
synchronously lives one layer down, like stapel-core itself.
Provenance: port of the categories/feature_types engine and the
ads validation pipeline from a legacy catalog app (see CHANGELOG for what
was fixed in transit).
Quick start
No INSTALLED_APPS entry, no urls — just import it:
from stapel_attributes import (
FeatureDef,
validate_dto,
normalize_to_dao,
validate_dto_structured,
)
configs = [
FeatureDef(slug="mileage", config={"type": "int", "min": 0, "postfix": "km"}),
FeatureDef(slug="condition", config={"type": "bool"}, mandatory=True),
]
payload = {"mileage": {"type": "int", "value": 120000},
"condition": {"type": "bool", "value": True}}
validate_dto(configs, payload) # raises ValidationError on failure
dao = normalize_to_dao(configs, payload) # {"mileage": {"type": "int", "value": 120000, "postfix": "km", "order": 0}, ...}
result = validate_dto_structured(configs, payload) # machine-readable batch result
Built-in types
int, float, string, bool, hex_color, select, date, header,
hierarchical_select, convertible_unit. Each type is a plugin: a Config
dataclass (schema), a DTO (client input), a DAO (stored value + display
metadata) and a handler (BaseFeatureType[TConfig, TDto, TDao]).
convertible_unit stores values in a canonical base unit per family
(length/weight/area/volume/temperature) and converts to/from the user-facing
unit — see MODULE.md for the storage/conversion/range-filter contract.
Other marketplace-specific types (size grids, ...) are not shipped — hosts register their own via the open registry (see MODULE.md for the worked example).
Settings
All configuration lives in the STAPEL_ATTRIBUTES namespace (dict setting,
flat setting, or env var — resolved lazily):
| Key | Default | Meaning |
|---|---|---|
EXTRA_TYPES |
[] |
Dotted paths of extra feature types, merged over the built-ins (each entry: a BaseFeatureType subclass or a module that registers types on import). |
Structured validation
Every validation failure carries a machine code end-to-end
(ValidationErrorCode) via FeatureValidationError — no message parsing.
Batch validators return ValidationBatchResult rows with error,
ref_value, localizable_error (an error.400.feature_* key) and params.
Extension points
See MODULE.md — the agent-facing map of every fork-free seam (settings, the type registry, serializer factories, translation-key hooks).
Admin UI
A schema-driven config editor (Lit 3 web components) ships with the package.
Each type declares its admin form in Python (config_form() → field-kinds); the
committed bundle renders it, so a new type needs zero JS for standard kinds. Use
ConfigEditorWidget on a config JSONField:
from stapel_attributes import ConfigEditorWidget
class FeatureForm(forms.ModelForm):
class Meta:
widgets = {"config": ConfigEditorWidget()}
Two themes (--stapel-*, light + dark), en/ru locales (merge without fork via
ADMIN_LOCALES), and JS widget registries for exotic types. See MODULE.md
"Admin UI" and docs/done/attributes-admin-ui.md. Frontend source is in static_src/
(npm test / npm run build); the built bundle is committed — consumers need no
Node.
Development
pip install -e . && pip install pytest pytest-django ruff
./setup-hooks.sh
pytest tests/
License
MIT — see LICENSE.
This page is assembled by stapel-readme from docs/readme.md plus the contract artifacts in docs/. Edit the prose in docs/readme.md; the badges, facts and links above and below it are generated — do not hand-edit README.md.
Metadata
Release files for stapel-attributes 0.9.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| stapel_attributes-0.9.4.tar.gz | 197.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| stapel_attributes-0.9.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 449.7 kB
Release files / stapel_attributes-0.9.4.tar.gz
| Download URL | stapel_attributes-0.9.4.tar.gz |
|---|---|
| Size | 197.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
991d42a1b57b4126acbacbcb9edfbbb0993d31fa455aa4f29563ba37090b495c
|
|
BLAKE2b-256 checksum How to use checksums |
383f7b1deef7e2dc074a0d9af9d6c121787259beec5330bad04c64017e8d1b08
|
| 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 8, 2026.
Transparency logRelease files / stapel_attributes-0.9.4-py3-none-any.whl
| Download URL | stapel_attributes-0.9.4-py3-none-any.whl |
|---|---|
| Size | 252.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
18922b0c1a319e7d36331b6bfe4a0d9c3ce91e60165fd9ca1066b4b7055a4d84
|
|
BLAKE2b-256 checksum How to use checksums |
b27a265660dfa61d8766377b3b31d7470b0bf52121fe5d44fc2ea75a3cb5756a
|
| 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 8, 2026.
Transparency log