Skip to main content
PyPepper

PyPepper

Composable building blocks for Python microservices.
Build faster. Live more.

PyPI Docs CI Coverage Python License

In memory of my father, who passed away in 2023 from COVID-19.


PyPepper is a small toolkit—not a full framework—for wiring services: HTTP / SSE, FSM, a workflow scheduler, signed events, thin DB helpers, and optional OpenTelemetry tracing. Supports Python 3.10–3.14.

pip install pypepper

Documentation

Getting Started · Tutorial · Architecture · Guides · API Reference

Source under docs/. Local preview: make docs-serve.

Domains

Package Role
Common pypepper.common Config, logging, context, cache, crypto, utilities
Event pypepper.event Signed domain events with JSON marshal
FSM pypepper.fsm Event-triggered state machine with rollback
Scheduler pypepper.scheduler Job → Channel → Worker → Workflow + pluggable job stores
Network pypepper.network FastAPI HTTP server and SSE subsystem
Helper pypepper.helper MySQL / PostgreSQL / MongoDB connectors

Highlights

Network FastAPI HTTP + SSE; header API-key auth and rate limits (auth-off needs PYPEPPER_SSE_ALLOW_AUTH_OFF) → guide
FSM & events Rollback on handler failure; signed JSON payloads → guide
Scheduler Rounds, soft timeouts, and retries; durable job-store fail-fast → guide
Tracing Opt-in OpenTelemetry (console / local Jaeger) → guide
Quality PEP 561 py.typed · ruff + mypy CI · line + branch coverage ≥ 90%
Data Thin DB helpers → guide

Quick start

Requires Python 3.10–3.14. uv ≥ 0.10.7 is recommended for local installs.

make build-prepare

SSE example (set a key; default config enables authentication):

export PYPEPPER_SSE_API_KEY=your-local-key
python example/sse/app.py

HTTP example:

python example/server/app.py --config ./conf/app.config.yaml

Scheduler end-to-end example: python example/scheduler/app.py.

Full walkthrough: Getting Started · First service tutorial.

Developer commands
make lint     # ruff + mypy
make check    # lint + mutable class-attr guard
make test     # check + pytest (coverage ≥ 90%, branch on)
make docs     # mkdocs build --strict
make audit    # pip-audit on requirements.txt and locked uv.lock
make docker   # local image
make clean

Contributing

See CONTRIBUTING.md for setup, Conventional Commits, and PR expectations. Release tags: docs/guides/release.md.

Security

See SECURITY.md for supported versions and private reporting. Leaving SSE authentication off without PYPEPPER_SSE_ALLOW_AUTH_OFF is rejected by the library (HTTP 503).

Metadata

Release files for pypepper 0.6.6

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

Source distribution (sdist)

Source distribution for pypepper 0.6.6
File Size Uploaded
pypepper-0.6.6.tar.gz 284.3 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for pypepper 0.6.6
File Interpreter ABI Platform
pypepper-0.6.6-py3-none-any.whl Python 3 none any Details

Total release size: 353.2 kB

Release files / pypepper-0.6.6.tar.gz

Download URL pypepper-0.6.6.tar.gz
Size 284.3 kB
Tags Source
SHA-256 checksum
How to use checksums
1c169ca70455bec7091ec7f393f7165b102b8b7eb573d50056780186c0535907
BLAKE2b-256 checksum
How to use checksums
1bc1836947306e5dfbc4edb53d8200b196147f53f9f340273882b41db56d8f47
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 18, 2026.

Transparency log

Release files / pypepper-0.6.6-py3-none-any.whl

Download URL pypepper-0.6.6-py3-none-any.whl
Size 68.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
a4cd3b091921cf8f3b64aac20a06270af5f7d353716b4b87436239dbe90e00e2
BLAKE2b-256 checksum
How to use checksums
a713226a8fdbf77a157be66472e65c8461617b02e52a3317b808b9015ed2433b
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 18, 2026.

Transparency log

Release history Release notifications | RSS feed

0.7.2

2 release files

0.7.1

2 release files

0.7.0

2 release files

This release

0.6.6 This release

2 release files

0.6.5

2 release files

0.6.4

2 release files

0.6.3

2 release files

0.6.2

2 release files

0.6.1

2 release files

0.6.0

2 release files

0.4.6

2 release files

0.4.5

2 release files

0.4.4

2 release files

0.4.3

2 release files

0.4.1

2 release files

0.4.0

2 release files

0.3.8

2 release files

0.3.7

2 release files

0.3.6

2 release files

0.3.5

2 release files

0.3.3

2 release files

0.3.2

2 release files

0.3.1

2 release files

0.3.0

2 release files

0.2.1

2 release files

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