SPLENT feature: what a booking runs on its machine (model API, chat, JupyterLab) behind the portal
  • Python 75.9%
  • HTML 23.6%
  • Shell 0.4%
  • Mako 0.1%
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
2026-11-14 21:27:23 +00:00
src One chat sizer that never lets the card spill over 2026-11-14 22:26:07 +01:00
.gitignore feat: scaffold splent_feature_lab_sessions with splent feature:create 2026-11-13 17:35:03 +00:00
COPYING feat: scaffold splent_feature_lab_sessions with splent feature:create 2026-11-13 17:35:03 +00:00
COPYING.LESSER feat: scaffold splent_feature_lab_sessions with splent feature:create 2026-11-13 17:35:03 +00:00
MANIFEST.in feat: scaffold splent_feature_lab_sessions with splent feature:create 2026-11-13 17:35:03 +00:00
pyproject.toml chore: release splent-io/splent_feature_lab_sessions to v0.1.32 2026-11-14 21:27:23 +00:00
README.md feat: scaffold splent_feature_lab_sessions with splent feature:create 2026-11-13 17:35:03 +00:00

splent_feature_lab_sessions

The lab_sessions feature of a SPLENT product line.

A SPLENT feature is a Python package that a product composes with others: its models, routes, services, templates and hooks are registered when the product starts. What this feature provides and requires is listed in the [tool.splent.contract] section of pyproject.toml, which splent feature:contract --write keeps in sync with the source.

Use it in a product

splent feature:add splent_feature_lab_sessions

Develop

splent feature:test splent_feature_lab_sessions
splent feature:contract splent_feature_lab_sessions

Release

splent feature:release splent_feature_lab_sessions --dry-run --bump patch
splent feature:release splent_feature_lab_sessions

The first command rehearses the release and changes nothing. The second publishes it to the git forge and to PyPI, and a PyPI version is permanent.