Inbound
Inbound is an asyncio framework for building event-driven systems in Python. It provides a seamless interface for working with different Message Brokers, including In-memory, RabbitMQ, and Kafka.
Features
- Asynchronous Operations: Build scalable and responsive systems with asyncio.
- Multiple Broker Support: Easily switch between In-memory, RabbitMQ, and soon to be more.
- Elegant API: Subscribe to channels, publish events, and listen to event streams with a simple and intuitive interface.
- Serialization Flexibility: Choose between serializers like msgpack and json based on your requirements or bring your own.
- Streamlined Callbacks API: Implement event-based systems quickly and effectively.
Quick Start
Installation
pip install python-inbound
Basic Usage
import asyncio
from inbound import EventBus
async def consume(bus: EventBus):
async with bus.subscribe("test-channel") as stream:
async for envelope in stream:
# Get the event from the envelope
event = envelope.event
print(event)
# After processing the event, acknowledge it
await envelope.ack()
# Unless you want to reject the event
# await envelope.nack()
async def produce(bus: EventBus):
coros = [
bus.publish(
channel="test-channel",
type="test-event",
data={"message": f"Hello World {i}"},
)
for i in range(20)
]
await asyncio.gather(*coros)
async def main():
event_bus = EventBus()
tasks = [asyncio.create_task(consume(event_bus)), asyncio.create_task(produce(event_bus))]
async with event_bus:
await asyncio.wait(tasks, return_when=asyncio.FIRST_COMPLETED)
if __name__ == "__main__":
asyncio.run(main())
Using Callbacks API
import asyncio
from inbound import CallbackGroup, Event, broker_from_url
group = CallbackGroup()
@group.callback("test-channel", "test-event")
def callback(event: Event):
# Note: Envelopes are automatically acknowledged
# for callbacks
print(event)
async def main():
event_bus = EventBus(broker=broker_from_url("memory://?serializer=msgpack"))
event_bus.add_group(group)
async with event_bus:
for i in range(3):
await event_bus.publish(
channel="test-channel",
type="test-event",
data={"message": f"Hello World {i}"},
)
await asyncio.sleep(0.01)
await event_bus.wait_until_finished()
if __name__ == "__main__":
asyncio.run(main())
You can find more examples in the examples directory.
Documentation
For comprehensive documentation, including advanced features and configurations, refer to Link to Documentation.
License
This project is licensed under MIT License.
Support & Feedback
If you encounter any issues or have feedback, please open an issue. We'd love to hear from you!
Made with ❤️ by Emergent Methods
Metadata
Release files for python-inbound 1.0.11
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| python_inbound-1.0.11-py3-none-any.whl | Python 3 | none | any | Details for python_inbound-1.0.11-py3-none-any.whl |
Release files / python_inbound-1.0.11-py3-none-any.whl
| Download URL | python_inbound-1.0.11-py3-none-any.whl |
|---|---|
| Size | 18.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b5d89e35d4a756d31fefca0b8a93ec97672b50d71d41b37a5eb31f316252e66c
|
|
BLAKE2b-256 checksum How to use checksums |
1d5fcb5c67e05a386ca4876fc47077ed43c35c257c0686c5025b5e3c9411bfce
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.6.7
|
Security for python-inbound 1.0.11
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.