aioartemis
asyncio-native AMQP 1.0 client for ActiveMQ Artemis, built for running behind load balancers and failing over between nodes.
- Reconnects to the next node on any connection loss, with jittered exponential backoff, and re-attaches senders and subscriptions.
- At-least-once delivery with explicit outcomes: ambiguous sends raise
ConnectionLostwith themessage_idto retry with;accept,nack,releaseandrejectmap to what Artemis does. - Built on Qpid Proton, whose event loop runs on a thread of its own, so heartbeats keep flowing while your event loop is busy.
Installation
pip install aioartemis
Python 3.12 or newer. aioartemis is pure Python, but its AMQP engine, python-qpid-proton, is published
only as a source distribution and compiles against the system's OpenSSL, so install the build
dependencies first, e.g. on Debian/Ubuntu:
apt-get install build-essential pkg-config libssl-dev
Without the OpenSSL headers it still installs, silently without TLS. See Installation for other systems and how to check.
Usage
import asyncio
from contextlib import suppress
from aioartemis import Client, DeliveryLost
async def main() -> None:
urls = ["amqp://artemis-1:5672", "amqp://artemis-2:5672"]
async with Client(urls, user="app", password="secret") as client:
await client.send("orders", {"id": 42})
async with client.subscribe("orders", prefetch=10) as orders:
async for message in orders:
print(message.body)
# The connection dropped since the message arrived: the broker
# redelivers it, so there is nothing left to settle.
with suppress(DeliveryLost):
await message.accept()
asyncio.run(main())
Documentation
https://smirnoffmg.dev/aioartemis/
- Delivery guarantees: duplicates, ordering, settling messages
- Failover and load balancers: reconnects, backoff, limitations
- Errors: what every exception means
- API reference
Examples
examples/ has runnable scripts for retrying ambiguous sends, an idempotent consumer, graceful shutdown, failover and topics, with a Docker Compose file for two local nodes.
License
Apache License 2.0, see LICENSE.
Contributing
See CONTRIBUTING.md.
Metadata
Release files for aioartemis 0.1.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 | Actions |
|---|---|---|---|---|
| aioartemis-0.1.1.tar.gz | 30.4 kB | With provenance | Details for aioartemis-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| aioartemis-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for aioartemis-0.1.1-py3-none-any.whl |
Total release size: 54.1 kB
Release files / aioartemis-0.1.1.tar.gz
| Download URL | aioartemis-0.1.1.tar.gz |
|---|---|
| Size | 30.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ccbf8918267e5dbacbe3c50d62b1d97e3d05492ad1809ad4520fba1d315f34c8
|
|
BLAKE2b-256 checksum How to use checksums |
ba193528e09c5207489d70351ae022d502fe77c0159d4a262f3bb0177e2d3400
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 17, 2026.
Transparency logRelease files / aioartemis-0.1.1-py3-none-any.whl
| Download URL | aioartemis-0.1.1-py3-none-any.whl |
|---|---|
| Size | 23.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2a4b8ae1f4cf45bfd663ca23d04bee9c07a60c099eb41bfd264c3683f73c1662
|
|
BLAKE2b-256 checksum How to use checksums |
dbed65e2c2c764ad6a1c305f747c530f224d66ee4f129b72651304dc3fdc3fa2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 17, 2026.
Transparency logSecurity for aioartemis 0.1.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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for aioartemis-0.1.1.tar.gz
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 Nov 17, 2026.
Transparency logA 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.