python-cq
python-cq is an async-first Python library for organizing code around CQRS. It separates reads (queries), writes (commands), and notifications (events) into dedicated message buses, and lets you plug in any dependency injection framework behind a small protocol.
What is CQRS?
CQRS (Command Query Responsibility Segregation) splits read operations from write operations. Each operation has a single, well-defined responsibility, which:
- clarifies intent: a
CreateUserCommanddoes one thing, and its name says so; - keeps handlers small: one message, one handler, easy to test in isolation;
- makes side effects explicit: events fan out to subscribers without coupling the producer to them.
CQRS is often discussed alongside distributed systems and Event Sourcing, but the pattern is just as useful in a local or monolithic application. The boundaries it draws are valuable on their own.
Three message types
| Type | Intent | Handlers | Returns |
|---|---|---|---|
Command |
Change the state of the system | Exactly one | The handler's return value |
Query |
Read state without side effects | Exactly one | The handler's return value |
Event |
Notify that something has happened | Zero, one, or many | Nothing |
A Command is allowed to return a value (for convenience, typically an id or a result object), but that does not mean it should be used as a query. Keep intent clear.
Installation
Requires Python 3.12 or higher.
With the default DI backend (python-injection, recommended):
pip install "python-cq[injection]"
Without dependency injection (you will need to implement a DIAdapter):
pip install python-cq
Quickstart
import asyncio
from cq import CommandBus, command_handler
from dataclasses import dataclass
from injection import inject
@dataclass
class CreateUserCommand:
name: str
email: str
@command_handler
class CreateUserHandler:
async def handle(self, command: CreateUserCommand) -> int:
# ... persist the user, return its id
return 42
@inject
async def main(bus: CommandBus[int]) -> None:
command = CreateUserCommand(name="Ada", email="ada@example.com")
user_id = await bus.dispatch(command)
print(f"Created user {user_id}")
asyncio.run(main())
The decorator registers the handler against the type of its first handle parameter. The bus is resolved by the DI container and dispatched to that handler.
Prerequisites
Familiarity with the following helps you get the most out of python-cq:
- CQRS, in particular the distinction between Commands, Queries, and Events.
- Domain Driven Design (DDD), particularly aggregates and bounded contexts, which complement CQRS well.
Metadata
Release files for python-cq 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 | Provenance | |
|---|---|---|---|---|
| python_cq-0.25.1.tar.gz | 16.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| python_cq-0.25.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 39.3 kB
Release files / python_cq-0.25.1.tar.gz
| Download URL | python_cq-0.25.1.tar.gz |
|---|---|
| Size | 16.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ba881d6a20180827cff66bd5c5a1f1db1a42870853ad01c502f24e6a4bedb71e
|
|
BLAKE2b-256 checksum How to use checksums |
4324af9848128283337e765a3591a3d85033bb1774c9c76ef9e3a36832465fa8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.4 {"installer":{"name":"uv","version":"0.13.4","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / python_cq-0.25.1-py3-none-any.whl
| Download URL | python_cq-0.25.1-py3-none-any.whl |
|---|---|
| Size | 23.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
16514e2934c66f5638db42e3de1e64b0777060a4f3e8b19fb85f6def35bd051c
|
|
BLAKE2b-256 checksum How to use checksums |
443e3f511bf559c206beabe7a0ef77b2e3bd00db9295c7888fe6fd690bd4a96b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.4 {"installer":{"name":"uv","version":"0.13.4","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for python-cq 0.25.1
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.