pico-rabbitmq
RabbitMQ pub-sub for the pico ecosystem: @consumer methods and declarative @publisher clients over aio-pika. Covers what pico-celery does not: events, fan-out, topic routing.
Installation
pip install pico-rabbitmq
Quick start
rabbitmq:
url: amqp://guest:guest@rabbit.internal/
Consume — a component method per queue, JSON body decoded for you:
from pico_ioc import component
from pico_rabbitmq import consumer
@component
class OrderProjections:
@consumer("orders-projection", exchange="events", routing_key="orders.*")
async def on_order_event(self, message: dict):
...
Publish — stubs, like a pico-httpx client:
from pico_rabbitmq import publisher, publish
@publisher
class OrderEvents:
@publish(exchange="events", routing_key="orders.created")
def order_created(self, message): ...
Semantics:
- Consumers and publishers run on a dedicated background loop — works in sync scripts, FastAPI apps and workers alike, no lifespan wiring.
- Each message resolves its component through the container (prototype scope = fresh instance per message).
- Ack on success; on exception the message is logged and rejected without requeue (configure a dead-letter exchange to keep failures).
- Sync publish stubs block until the broker confirms; async stubs await it.
- Queues and named exchanges are declared durable; the connection closes on container shutdown.
Documentation
Full documentation: https://dperezcabrera.github.io/pico-rabbitmq/
Built for AI-assisted development
pico-rabbitmq is part of an ecosystem designed for humans and coding agents building software together. Every package ships AGENTS.md working conventions, an llms.txt machine-readable docs index and documented behaviour pinned by regression tests; pico-testing gives agents a verification loop for their own changes, and releases are gated by the whole ecosystem booting together against real infrastructure. The full story: Built for AI-assisted development.
Install the agent skills for Claude Code or OpenAI Codex:
curl -sL https://raw.githubusercontent.com/dperezcabrera/pico-skills/main/install.sh | bash
The pico-conventions skill teaches the assistant this module's API surface and invariants; /add-component and /add-tests scaffold components and tests that use it.
License
MIT
Metadata
Release files for pico-rabbitmq 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| pico_rabbitmq-0.1.2.tar.gz | 27.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pico_rabbitmq-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 37.2 kB
Release files / pico_rabbitmq-0.1.2.tar.gz
| Download URL | pico_rabbitmq-0.1.2.tar.gz |
|---|---|
| Size | 27.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
79ff5cf945417d2eb5a7cceac25772ee84db4f3eccc71e4c63941000b307cb66
|
|
BLAKE2b-256 checksum How to use checksums |
72a4128860c0bdcb3243f2d47f19773fb09ba70a858438b3e723b8fa426edf2a
|
| 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 29, 2026.
Transparency logRelease files / pico_rabbitmq-0.1.2-py3-none-any.whl
| Download URL | pico_rabbitmq-0.1.2-py3-none-any.whl |
|---|---|
| Size | 9.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2029781e47cbbd1b04481c78addf6ae15f697587a9b1b703967ffc00b05a2562
|
|
BLAKE2b-256 checksum How to use checksums |
50b9e389d8dd2da412b97017aaaf486cd4e6baf6148486b55499c053938a1ad5
|
| 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 29, 2026.
Transparency log