Skip to main content

capo-sqs: typed, async Python SDK for AWS SQS

capo-sqs is a typed Python SDK for AWS SQS. It has an async client, AsyncSQSClient, for asyncio and trio, and a sync client, SQSClient, 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/sqs/

Installation

pip install capo-sqs

Usage

from capo_sqs import AsyncSQSClient


async def main():
    async with AsyncSQSClient() as sqs:
        # Example: call the add_permission operation
        response = await sqs.add_permission()
        print(response)

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_sqs import AsyncSQSClient


async def main():
    async with AsyncSQSClient() as sqs:
        # Example: paginate over list_dead_letter_source_queues
        async for item in sqs.iter_list_dead_letter_source_queues():
            print(item)

Error Handling

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

from capo_sqs import AsyncSQSClient
from capo_sqs.error import InvalidAddress


async def main():
    async with AsyncSQSClient() as sqs:
        try:
            await sqs.add_permission()
        except InvalidAddress 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_sqs import AsyncSQSClient


async def main():
    async with AsyncSQSClient() as sqs:
        # Default: 3 attempts for every operation
        response = await sqs.add_permission()

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

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

Metadata

Release files for capo-sqs 0.15.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-sqs 0.15.0
File Size Uploaded Provenance
capo_sqs-0.15.0.tar.gz 140.1 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-sqs 0.15.0
File Interpreter ABI Platform
capo_sqs-0.15.0-py3-none-any.whl Python 3 none any Details

Total release size: 382.0 kB

Release files / capo_sqs-0.15.0.tar.gz

Download URL capo_sqs-0.15.0.tar.gz
Size 140.1 kB
Tags Source
SHA-256 checksum
How to use checksums
aeb6c8362f102166b763cf16a40ae8b5bc0138ab1765809da4bebb162597f7a1
BLAKE2b-256 checksum
How to use checksums
7934557f850fb6e4d02145972a77fa2c697530c01a1702306b2e5a01b0978813
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_sqs-0.15.0-py3-none-any.whl

Download URL capo_sqs-0.15.0-py3-none-any.whl
Size 241.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
f353fc20a8110f250ca2956a12ecd278559d1af79b1a67bc25bffb46639b4c4a
BLAKE2b-256 checksum
How to use checksums
936c8c921544fa828bb28af97f7c05395b3460e3cd7a6aba9a54ac0561fb8efa
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-sqs 0.15.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