Skip to main content

stonedog-remembers

A small, message-driven state management library for Python, inspired by the predictable state-container pattern popularized by Redux. It gives you a centralized, observable bag of state that you read and write through simple dot-path keys (e.g. "job.bins"), with change events you can subscribe to and optional JSON persistence.

It ships two front ends over the same dot-path engine:

  • Store — a synchronous store. Best for ordinary synchronous code that just wants central, observable runtime state without an event loop.
  • StonedogRemembers — an asyncio, Redux-style store driven by an action queue and an event queue. Best for long-running async applications.

Both share the exported helpers get_nested_value(path, data) and set_nested_value(path, value, data).

Installation

pip install stonedog-remembers

The import name is stonedog_remembers:

from stonedog_remembers import Store, StonedogRemembers, get_nested_value, set_nested_value

Dot-path convention

State is a nested dict, and every read/write addresses a value by a dot-separated path:

  • "user.theme"state["user"]["theme"]
  • numeric segments index into lists: "items.0.name"state["items"][0]["name"]
  • reads of a missing or non-traversable path return None (or your supplied default on Store.get).
  • writes auto-create intermediate dicts as needed. A write fails (returns False) only if a segment can't be traversed or assigned — e.g. a list index out of range, or trying to descend into a scalar.

Quickstart — Store (synchronous)

from stonedog_remembers import Store

store = Store({"job": {"bins": 10, "sorted": 0}})

# read / write by dot-path
store.set("job.sorted", 1)            # -> True
store.get("job.sorted")               # -> 1
store.get("job.missing", default=0)   # -> 0 (missing path falls back)

# writes auto-create intermediate dicts
store.set("machine.state", "CARD_READY")
store.get_state()                     # deep copy of the whole state

# subscribe to change events; subscribe() returns an unsubscribe function
def on_change(event):
    print(event["path"], event["old_value"], "->", event["new_value"])

unsubscribe = store.subscribe(on_change)
store.set("job.sorted", 2)            # -> on_change fires
unsubscribe()                         # stop receiving events

Persistence

Store reads and writes plain JSON:

store.save("state.json")                 # write current state to disk
restored = Store(state_file="state.json")  # load state at construction
restored.get("job.bins")                 # -> 10

# a Store created with state_file remembers it, so save() needs no argument
live = Store(state_file="state.json")
live.set("job.sorted", 5)
live.save()                              # persists back to state.json

Loading a missing file or malformed JSON starts from an empty state (a warning is logged) rather than raising, so a first run "just works".

Quickstart — StonedogRemembers (asynchronous)

StonedogRemembers processes actions off a queue and emits events onto another queue. You dispatch SET_STATE actions and consume STATE_CHANGED events.

import asyncio
from stonedog_remembers import StonedogRemembers

async def main():
    store = StonedogRemembers("initial_state.json")
    await store.load_initial_state()      # empty state if the file is absent
    store.start_processing()              # start the background action processor

    # observe state changes
    events = store.subscribe_events()     # an asyncio.Queue of event dicts

    await store.dispatch({
        "type": StonedogRemembers.ACTION_TYPE_SET_STATE,   # "SET_STATE"
        "path": "user.theme",
        "value": "dark",
    })

    event = await events.get()
    # {'type': 'STATE_CHANGED', 'path': 'user.theme',
    #  'old_value': None, 'new_value': 'dark', 'action_source': {...}}
    print(event["path"], "->", event["new_value"])
    print(store.get_current_state())      # deep copy of the whole state

    await store.stop_processing()

asyncio.run(main())

The subscribe / events model

  • Store notifies synchronously: each set() that changes state calls every subscriber callback with a STATE_CHANGED event ({"type", "path", "old_value", "new_value"}). A raising subscriber is logged and isolated — it won't break the store or other subscribers.
  • StonedogRemembers is asynchronous: subscribe_events() returns an asyncio.Queue. Each applied SET_STATE puts a STATE_CHANGED event (which also carries action_source) on that queue for your consumer coroutine to await. Actions with no path, unknown action types, and writes that can't be applied are ignored and emit no event.

Development

This is a Poetry (PEP 621) project. Tests run under pytest with a coverage gate:

pip install pytest pytest-asyncio pytest-cov
pytest        # runs the suite and enforces >=90% line coverage

pythonpath = ["src"] is set in pyproject.toml, so tests import stonedog_remembers directly without a manual PYTHONPATH.

License

MIT

Renamed from roz-remembers

This library was published as roz-remembers through 0.2.0. It is the same library under the StoneDogCode name: the distribution is now stonedog-remembers, the import is stonedog_remembers, and the async store class is StonedogRemembers.

from roz_remembers import RozRemembers            # before
from stonedog_remembers import StonedogRemembers  # now

RozRemembers remains exported as a deprecated alias — it is the same object, not a subclass, so isinstance checks and the ACTION_TYPE_* / EVENT_TYPE_* class attributes behave identically either way.

The old roz-remembers distribution stays on PyPI so existing installs keep working, but it receives no further releases.

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

stonedog_remembers-0.3.0.tar.gz (7.5 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

stonedog_remembers-0.3.0-py3-none-any.whl (8.3 kB view details)

Uploaded Python 3

File details

Details for the file stonedog_remembers-0.3.0.tar.gz.

File metadata

  • Download URL: stonedog_remembers-0.3.0.tar.gz
  • Upload date:
  • Size: 7.5 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: uv/0.11.26 {"installer":{"name":"uv","version":"0.11.26","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

File hashes

Hashes for stonedog_remembers-0.3.0.tar.gz
Algorithm Hash digest
SHA256 ffafe71085a0c08bcadf7b08f96f54aa7dfe89c3182a808ae5679bae05f2bd2d
MD5 2a47287e696bbbfb66f4f20936e17c54
BLAKE2b-256 ec8d6a758a4001afffd0670ec593ce5ac6127542cb9f5269d5493c6599081bd7

See more details on using hashes here.

File details

Details for the file stonedog_remembers-0.3.0-py3-none-any.whl.

File metadata

  • Download URL: stonedog_remembers-0.3.0-py3-none-any.whl
  • Upload date:
  • Size: 8.3 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: uv/0.11.26 {"installer":{"name":"uv","version":"0.11.26","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

File hashes

Hashes for stonedog_remembers-0.3.0-py3-none-any.whl
Algorithm Hash digest
SHA256 ea2a4075bee5de7c592d9c5fd5fc0a997572c1e360fec51f027720839c2766b1
MD5 f339af8325643e9d139f188710ce37f0
BLAKE2b-256 4701ef4fd61a9a498b7e33ae94ba09788c7b4cde3e9a8d08aef4162b54d7503d

See more details on using hashes here.

Release history Release notifications | RSS feed

0.4.0

2 files

0.3.1

2 files

This release

0.3.0 This release

2 files

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page