Skip to main content

capo-lambda: typed, async Python SDK for AWS Lambda

capo-lambda is a typed Python SDK for AWS Lambda. It has an async client, AsyncLambdaClient, for asyncio and trio, and a sync client, LambdaClient, 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/lambda/

Installation

pip install capo-lambda

Usage

from capo_lambda import AsyncLambdaClient


async def main():
    async with AsyncLambdaClient() as lambda_:
        # Example: call the delete_function operation
        response = await lambda_.delete_function()
        print(response["status_code"])

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_lambda import AsyncLambdaClient


async def main():
    async with AsyncLambdaClient() as lambda_:
        # Example: paginate over list_capacity_providers
        async for item in lambda_.iter_list_capacity_providers():
            print(item)

Streaming Request

Some operations accept a streaming request body. Pass an async iterator of bytes chunks, or the whole body as bytes, for the streaming parameter.

A plain iterator can be sent only once, so if a request fails after its body was transmitted the operation is not retried. To get retries for streamed uploads, pass a Body instead: it wraps a source that can be reopened, and every attempt streams a fresh copy. Body.from_path (sync client) and Body.async_from_path (async client, needs anyio) stream a file from disk; Body(opener) takes any context manager that yields a (stream, length) pair.

from capo_lambda import AsyncLambdaClient, Body


async def main():
    async with AsyncLambdaClient() as lambda_:
        # Example: call invoke_async with a streaming request body
        async def chunks():
            yield b'Hello, World!'

        response = await lambda_.invoke_async(invoke_args=chunks())
        print(response)

        # Or pass the whole body as bytes
        response = await lambda_.invoke_async(invoke_args=b'Hello, World!')
        print(response)

        # Or stream a file with Body: the file is reopened on every retry
        # and Content-Length is taken from its size, so no content_length needed
        response = await lambda_.invoke_async(invoke_args=Body.async_from_path("hello.txt"))
        print(response)

Waiters

Waiters poll an operation until a resource reaches a desired state. If the operation supports waiters it will have a wait_until_ prefixed method.

from capo_lambda import AsyncLambdaClient


async def main():
    async with AsyncLambdaClient() as lambda_:
        # Example: wait for function_exists
        await lambda_.wait_until_function_exists(max_wait_time=300)

Error Handling

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

from capo_lambda import AsyncLambdaClient
from capo_lambda.error import InvalidParameterValueException


async def main():
    async with AsyncLambdaClient() as lambda_:
        try:
            await lambda_.delete_function()
        except InvalidParameterValueException 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_lambda import AsyncLambdaClient


async def main():
    async with AsyncLambdaClient() as lambda_:
        # Default: 3 attempts for every operation
        response = await lambda_.delete_function()

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

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

Metadata

Release files for capo-lambda 0.23.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-lambda 0.23.0
File Size Uploaded Provenance Actions
capo_lambda-0.23.0.tar.gz 397.8 kB Without provenance Details for capo_lambda-0.23.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for capo-lambda 0.23.0
File Interpreter ABI Platform Actions
capo_lambda-0.23.0-py3-none-any.whl Python 3 none any Details for capo_lambda-0.23.0-py3-none-any.whl

Total release size: 1.2 MB

Release files / capo_lambda-0.23.0.tar.gz

Download URL capo_lambda-0.23.0.tar.gz
Size 397.8 kB
Tags Source
SHA-256 checksum
How to use checksums
7376b1f0f4a236b322e45d7a2dc320d96d92be41fa8978049186774f58d394eb
BLAKE2b-256 checksum
How to use checksums
e7c49080b8cba7962e5702cb17b7d1a38c47e4a3ed798d2355257aeec2b26af8
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_lambda-0.23.0-py3-none-any.whl

Download URL capo_lambda-0.23.0-py3-none-any.whl
Size 838.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
91e200d77e1b6eb1092d631f7018e163ab77ff02c3ba9244df04af69aff0f930
BLAKE2b-256 checksum
How to use checksums
d092f435bec530a90f86485cc0c432e989b5a555a1e87b5b6263a4d5f2386a80
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-lambda 0.23.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.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

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