Skip to main content

capo-mq: typed, async Python SDK for AWS MQ

capo-mq is a typed Python SDK for AWS MQ. It has an async client, AsyncmqClient, for asyncio and trio, and a sync client, mqClient, with the same methods. Requests and responses are typed with TypedDicts, so your editor and type checker know every field.

It is part of capo, a community-driven alternative to boto3 and aioboto3, built on its own HTTP stack instead of botocore and generated from the official AWS Smithy models. Documentation: https://capo-sdk.dev/services/mq/

Installation

pip install capo-mq

Usage

from capo_mq import AsyncmqClient


async def main():
    async with AsyncmqClient() as mq:
        # Example: call the create_broker operation
        response = await mq.create_broker()
        print(response["broker_arn"])

Pagination

Some operations in this SDK support pagination. If the operation supports pagination it will have an iter_ prefixed method that returns an async iterator.

from capo_mq import AsyncmqClient


async def main():
    async with AsyncmqClient() as mq:
        # Example: paginate over describe_shared_resources
        async for item in mq.iter_describe_shared_resources():
            print(item)

Error Handling

The SDK raises exceptions for errors returned by the API. Catch them to handle failures gracefully.

from capo_mq import AsyncmqClient
from capo_mq.error import BadRequestException


async def main():
    async with AsyncmqClient() as mq:
        try:
            await mq.create_broker()
        except BadRequestException as e:
            print(f"Error: {e}")
            print(e.data)  # additional error data

Retrying

The SDK retries failed operations automatically. Retry behaviour follows the Smithy specification: errors are retried based on their is_retryable and is_throttling_error attributes. Throttling errors use a longer base delay. Network-level failures (connection errors and timeouts) are also retried. Non-retryable errors, such as client errors without the @retryable trait, are raised immediately without further attempts.

The number of attempts defaults to 3 and can be changed at the client level via retry_max_attempts, or per call via config_overrides.

from capo_mq import AsyncmqClient


async def main():
    async with AsyncmqClient() as mq:
        # Default: 3 attempts for every operation
        response = await mq.create_broker()

        # Override per operation
        response = await mq.create_broker(config_overrides={"retry_max_attempts": 5})

        # Disable retries for this call
        response = await mq.create_broker(config_overrides={"retry_max_attempts": 1})

Metadata

Release files for capo-mq 0.9.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for capo-mq 0.9.0
File Size Uploaded Provenance
capo_mq-0.9.0.tar.gz 105.6 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-mq 0.9.0
File Interpreter ABI Platform
capo_mq-0.9.0-py3-none-any.whl Python 3 none any Details

Total release size: 313.0 kB

Release files / capo_mq-0.9.0.tar.gz

Download URL capo_mq-0.9.0.tar.gz
Size 105.6 kB
Tags Source
SHA-256 checksum
How to use checksums
e5e992c7303c1f5814ffa6ee57f91ce0c1e77464bc024266ec99e7224b40a183
BLAKE2b-256 checksum
How to use checksums
ccf32030afb4c9aab614822b9086a4c570e5b8eeeb1ccfbb33714838579c21b2
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","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 / capo_mq-0.9.0-py3-none-any.whl

Download URL capo_mq-0.9.0-py3-none-any.whl
Size 207.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
c858ccca46805e2e23bbf26aeeb9e6644e44979d49faeb85f6195ee1b27b0bbc
BLAKE2b-256 checksum
How to use checksums
86f56cefab9255ed76056107d6430e10fdd8a0802428dc71e5ea0421e5fd2760
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","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 capo-mq 0.9.0

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page