Lightweight multi-threaded job framework https://doc.olog.io/execlib
Go to file
2024-05-14 15:49:23 -07:00
docs add router builder class, fix interupts for ListenerServer 2024-05-09 00:39:42 -07:00
execlog clean up repo files, README, auxiliary files (pre-BFG) 2024-05-14 15:49:23 -07:00
tests add callback timeouts, secondary thread pools, and frame directives to Router 2024-05-14 06:37:08 -07:00
.gitignore clean up repo files, README, auxiliary files (pre-BFG) 2024-05-14 15:49:23 -07:00
MANIFEST.in initial commit (public reset) 2024-04-19 18:43:52 -07:00
pyproject.toml clean up repo files, README, auxiliary files (pre-BFG) 2024-05-14 15:49:23 -07:00
README.md clean up repo files, README, auxiliary files (pre-BFG) 2024-05-14 15:49:23 -07:00
requirements.txt update docstrings to RST for Sphinx 2024-04-28 17:21:33 -07:00

Overview

execlog is a lightweight multi-threaded job framework written in Python. It implements a simple event-based model over core Python utilities like ThreadPoolExecutor to facilitate reactivity and manage concurrent responses.

There are a few top-level classes exposed by the package:

  • Router: Central event routing object. Routers facilitate route registration, allowing for pattern-based matching of events to arbitrary callback functions. For example, you could have a function that converts a PDF file to a collection images (callback), and want this function to be called for a new files (event) that match the glob *.pdf (pattern).
  • Listener: Connective event listening object, often created directly by router instances. Listeners pay attention to events arising along registered routes of an affiliated router, passing them through (after optional delays, debouncing, filtering, etc). In the above example, the associated Listener instance might wrap a tool like iNotify to dynamically respond to file events.
  • Server: Long-running process manager for listeners and optional live-reloading via HTTP. Interfaces with listener start() and shutdown() for graceful interruption.