lightfall-settings
Pure-Python model for Lightfall's scoped settings, shared by the Lightfall client and the logbook server so both compute identical answers.
- Scopes:
facility→beamline:<bl>→branch:<branch>→user:<sub>, ordered broad to specific in aScopeChain. - Scope roles from Keycloak group paths (
/beamlines/<bl>/<role>,/beamlines/<bl>/branch/<branch>/<role>,/beamlines/_all/<role>,/BCG_staff). SettingSpec: which scopes a key may be set at,overrideorunionpolicy, write role, lockability. Specs serialize to JSON for server-side key proposals and approvals.- Resolver: effective value of a key across a chain of scope snapshots, honouring locks.
- Write rules: the server-side checks for set / delete / lock / unlock / publish.
No Qt, no HTTP. Depends only on pydantic.
Install
pip install lightfall-settings
Development
../lightfall/.venv/Scripts/python -m pytest
../lightfall/.venv/Scripts/python -m ruff check .
License
BSD-3-Clause; see LICENSE.md and LEGAL.md.
1 maintainer
Metadata
1 maintainer
Release files for lightfall-settings 0.1.3
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 | |
|---|---|---|---|---|
| lightfall_settings-0.1.3.tar.gz | 17.9 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| lightfall_settings-0.1.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 32.7 kB
Release files / lightfall_settings-0.1.3.tar.gz
| Download URL | lightfall_settings-0.1.3.tar.gz |
|---|---|
| Size | 17.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ee7709474ccc7b91c9cbb766deb941ff5a9372bc8200cdfa8d9404c6b908775e
|
|
BLAKE2b-256 checksum How to use checksums |
67ff53e66b525810f596fe226944701f0ece4f0afa043af32ba88ee294408fcd
|
| 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 Oct 18, 2026.
Transparency logRelease files / lightfall_settings-0.1.3-py3-none-any.whl
| Download URL | lightfall_settings-0.1.3-py3-none-any.whl |
|---|---|
| Size | 14.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b8c6ded8506e04b6b4b6ac6c49e384684084119311d67d804c3bc3ce9ae3fad1
|
|
BLAKE2b-256 checksum How to use checksums |
6927c81777d3521314e7e7eb2a230833e4c57099478469457c6db87c3e83b649
|
| 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 Oct 18, 2026.
Transparency logSecurity for lightfall-settings 0.1.3
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for lightfall_settings-0.1.3.tar.gz
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 Oct 18, 2026.
Transparency logA 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.
