scitex-events 0.1.4

General-purpose async event bus (file-backed, JSON Lines) — standalone module from the SciTeX ecosystem

scitex-events

Zero-dep async event bus for the SciTeX ecosystem.

Full Documentation · uv pip install scitex-events[all]

---

Installation

pip install scitex-events

Architecture

scitex-events/
├── src/scitex_events/
│   ├── _emit.py         # write event to JSONL store
│   ├── _history.py      # latest / history / list_types
│   ├── _schemas.py      # event-type registry
│   └── _webhook.py      # optional cloud forwarder
└── tests/

1 Interfaces

Python API

import scitex_events as ev

# Emit an event (any kwargs become payload fields).
ev.emit("test_complete", project="figrecipe", status="success",
        payload={"exit_code": 0, "module": "stats"})

# Latest event of a given type.
ev.latest("test_complete")

# Recent history (newest first).
list(ev.history(limit=20))

# Schemas / introspection.
ev.list_types()
ev.get_type_info("test_complete")

Events are stored locally as JSON-Lines files (override path via SCITEX_EVENTS_DIR) and can optionally be forwarded to a cloud webhook.

Demo

flowchart LR
    Producer[ev.emit] --> JSONL[(JSONL store)]
    JSONL --> Latest[ev.latest]
    JSONL --> History[ev.history]
    JSONL -. optional .-> Webhook[Cloud webhook]

Quick Start

import scitex_events as ev

ev.emit("test_complete", project="figrecipe", status="success",
        payload={"exit_code": 0, "module": "stats"})

ev.latest("test_complete")     # most recent event of this type
list(ev.history(limit=20))     # recent history

Status

Standalone fork of scitex.events. Pure stdlib — zero runtime deps. The umbrella package's scitex.events import path is preserved via a sys.modules-alias bridge so existing code continues to work.

Part of SciTeX

scitex-events is part of SciTeX. Install via the umbrella with pip install scitex[events] to use as scitex.events (Python) or scitex events ... (CLI).

Four Freedoms for Research

0. The freedom to run your research anywhere — your machine, your terms.
1. The freedom to study how every step works — from raw data to final manuscript.
2. The freedom to redistribute your workflows, not just your papers.
3. The freedom to modify any module and share improvements with the community.

AGPL-3.0 — because we believe research infrastructure deserves the same freedoms as the software it runs on.

License

AGPL-3.0-only (see LICENSE).

---