Skip to main content

abstraction-config, in Python

Where a machine keeps its answer to "which store", and who said so. An administrator's machine-wide file, then this user's file, then the environment for one run — each overriding the last, key by key, with the origin of every answer kept beside it.

An application asks the machine and names no path. A key nothing set is absent, which means this machine does not have that tier: a normal answer, not an error.

This page is the Python package. The Go implementation, the file format and what is UNPROVEN are on the repository.

Install

Not on PyPI, and the names on PyPI are not ours. Clone the three repositories beside each other and install them in dependency order:

git clone https://github.com/openabstractions/abstraction-cas
git clone https://github.com/openabstractions/abstraction-watch
git clone https://github.com/openabstractions/abstraction-config

pip install ./abstraction-cas/python ./abstraction-watch/python
pip install ./abstraction-config/python

Python 3.9 or later.

An example that runs

import abstraction_config as config

store, why = config.job_store()
print("jobs live at:", store)
print("because:", why)

print(config.load().describe())

On a machine nobody has configured it prints the default and says so. It reads files and writes none, so running it changes nothing.

What an application calls

call what it does
job_store() (path, why) — where jobs live on this machine, and what decided
load() a Config: nas_store, store, log_sink, log_service, off. A file that cannot be read or parsed is skipped, with one line on stderr saying which
Config.origin(key) which authority answered for one key, and which file said so
Config.describe() what was found and where, for a status command
Config.stamp() differs whenever the answer differs, so a long-running process can ask whether anything moved instead of rebuilding
overridden() the keys the environment is deciding, whatever the files say
user_path() / machine_path() the conventional locations on this platform
watch(budget) a subscription that re-reads when the answer changes

The environment variables that override a file, one per key: ABSTRACTION_NAS_STORE, ABSTRACTION_STORE, ABSTRACTION_LOG, ABSTRACTION_LOG_SERVICE.

What may break

  • This module reads; it does not write. There is no save here. A setup step or the Go implementation writes the file.
  • A machine-wide file no administrator owns raises Untrusted rather than being obeyed. Ownership is what is checked, so a file on a filesystem that does not carry it is refused.
  • No conformance verdict. No scenario in the suite cites this layer yet — what is proven and what is not.
  • Not on any package index, and no release carries an API stability promise. Pin a commit you have read.
  • Every published transcript was produced on Windows or Linux. macOS is UNPROVEN throughout.

Apache-2.0. See LICENSE.

Metadata

Release files for abstraction-config 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for abstraction-config 0.1.0
File Size Uploaded Provenance Actions
abstraction_config-0.1.0.tar.gz 12.4 kB With provenance Details for abstraction_config-0.1.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for abstraction-config 0.1.0
File Interpreter ABI Platform Actions
abstraction_config-0.1.0-py3-none-any.whl Python 3 none any Details for abstraction_config-0.1.0-py3-none-any.whl

Total release size: 25.4 kB

Release files / abstraction_config-0.1.0.tar.gz

Download URL abstraction_config-0.1.0.tar.gz
Size 12.4 kB
Tags Source
SHA-256 checksum
How to use checksums
4d6487b3ec03150bfd77197cbc0494641ebcab1c8464fc839ff67acb7ea23c39
BLAKE2b-256 checksum
How to use checksums
3f9ee0e194e74bd5f458eaa2c9a62a56bb99c629ed6500d127bd16c2453f3cd9
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 10, 2026.

Transparency log

Release files / abstraction_config-0.1.0-py3-none-any.whl

Download URL abstraction_config-0.1.0-py3-none-any.whl
Size 13.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
fe4cb2a65dd09d296d623102d7c4c9b923024d02ca9a6e55fca13a74b52e2202
BLAKE2b-256 checksum
How to use checksums
5229e653912a131fe21f6d65f51f15ea19857c37bfa481e26aed1abdab967cb8
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 10, 2026.

Transparency log

Security for abstraction-config 0.1.0

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

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for abstraction_config-0.1.0.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 Sep 10, 2026.

Transparency log

A 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.

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page