Docket is a distributed background task system for Python functions with a focus on the scheduling of future work as seamlessly and efficiently as immediate work.
At a glance
from datetime import datetime, timedelta, timezone
from docket import Docket
async def greet(name: str, greeting="Hello") -> None:
print(f"{greeting}, {name} at {datetime.now()}!")
async with Docket() as docket:
await docket.add(greet)("Jane")
now = datetime.now(timezone.utc)
soon = now + timedelta(seconds=3)
await docket.add(greet, when=soon)("John", greeting="Howdy")
from docket import Docket, Worker
async with Docket() as docket:
docket.register(greet)
async with Worker(docket) as worker:
await worker.run_until_finished()
Hello, Jane at 2025-03-05 13:58:21.552644!
Howdy, John at 2025-03-05 13:58:24.550773!
Check out our docs for more details, examples, and the API reference.
Why docket?
⚡️ Snappy one-way background task processing without any bloat
📅 Schedule immediate or future work seamlessly with the same interface
⏭️ Skip problematic tasks or parameters without redeploying
🌊 Purpose-built for Redis streams
🧩 Fully type-complete and type-aware for your background task functions
💉 Dependency injection like FastAPI, Typer, and FastMCP for reusable resources
Installing docket
Docket is available on PyPI under the package name
pydocket. It targets Python 3.10 or above.
With uv:
uv pip install pydocket
or
uv add pydocket
With pip:
pip install pydocket
Docket requires a Redis server with Streams support (which was introduced in Redis 5.0.0). Docket is tested with:
- Redis 6.2, 7.4, and 8.6 (standalone and cluster modes)
- Valkey 8.1
- In-memory backend via burner-redis for testing
For testing without Redis, use the in-memory backend:
from docket import Docket
async with Docket(name="my-docket", url="memory://my-docket") as docket:
# Use docket normally - all operations are in-memory
...
See Testing with Docket for more details.
Hacking on docket
We use uv for project management, so getting set up
should be as simple as cloning the repo and running:
uv sync
The to run the test suite:
pytest
We aim to maintain 100% test coverage, which is required for all PRs to docket. We
believe that docket should stay small, simple, understandable, and reliable, and that
begins with testing all the dusty branches and corners. This will give us the
confidence to upgrade dependencies quickly and to adapt to new versions of Redis over
time.
To work on the documentation locally:
uv sync
uv run zensical serve
This will start a local preview server. The docs are built with
Zensical and configured in mkdocs.yml.
1 maintainer
Metadata
1 maintainer
Release files for pydocket 0.25.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| pydocket-0.25.1.tar.gz | 454.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pydocket-0.25.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 594.3 kB
Release files / pydocket-0.25.1.tar.gz
| Download URL | pydocket-0.25.1.tar.gz |
|---|---|
| Size | 454.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
999708a5e957eb1747615e3c681af773f603a66f0b9af120cd9ef9330e6666ba
|
|
BLAKE2b-256 checksum How to use checksums |
afe212a5d834a15c5f16d9fe80e90d6b5210957cf4b794bed580a64f2fa4e066
|
| 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 9, 2026.
Transparency logRelease files / pydocket-0.25.1-py3-none-any.whl
| Download URL | pydocket-0.25.1-py3-none-any.whl |
|---|---|
| Size | 140.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
acc8b87019c15804c22043223e6d84a9ec2a77203c4f6037f7c3c2a9ad2a6fca
|
|
BLAKE2b-256 checksum How to use checksums |
b77bcfee4fc1a6a7cb26ee79108e6e28f036ce85e330058bc3f7b0cd788c3b4a
|
| 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 9, 2026.
Transparency log
