Skip to main content

capo-evs: typed, async Python SDK for AWS EVS

capo-evs is a typed Python SDK for AWS EVS. It has an async client, AsyncevsClient, for asyncio and trio, and a sync client, evsClient, 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/evs/

Installation

pip install capo-evs

Usage

from capo_evs import AsyncevsClient


async def main():
    async with AsyncevsClient() as evs:
        # Example: call the get_account_settings operation
        response = await evs.get_account_settings()
        print(response["settings"])

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_evs import AsyncevsClient


async def main():
    async with AsyncevsClient() as evs:
        # Example: paginate over list_environments
        async for item in evs.iter_list_environments():
            print(item)

Error Handling

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

from capo_evs import AsyncevsClient
from capo_evs.error import InternalServerException


async def main():
    async with AsyncevsClient() as evs:
        try:
            await evs.get_account_settings()
        except InternalServerException 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_evs import AsyncevsClient


async def main():
    async with AsyncevsClient() as evs:
        # Default: 3 attempts for every operation
        response = await evs.get_account_settings()

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

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

Metadata

Release files for capo-evs 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-evs 0.9.0
File Size Uploaded Provenance
capo_evs-0.9.0.tar.gz 131.3 kB Without provenance Details

Built distribution (wheel)

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

Total release size: 366.8 kB

Release files / capo_evs-0.9.0.tar.gz

Download URL capo_evs-0.9.0.tar.gz
Size 131.3 kB
Tags Source
SHA-256 checksum
How to use checksums
3aa6254558c198c6a45611d3d7c5706e88399325ca83927b6342e1029ba0e822
BLAKE2b-256 checksum
How to use checksums
085202e6577a7cedffc8039fd20851cae1c00c3b3d55f483e2f556d64f9b6d62
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_evs-0.9.0-py3-none-any.whl

Download URL capo_evs-0.9.0-py3-none-any.whl
Size 235.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
863411f1a9dbed7fa4d0c591d3c82cadbd9632cd76047bd8a5722bde5bcc5cef
BLAKE2b-256 checksum
How to use checksums
c7d04989d567fe7ce4aa1f8a30bc83a78f0e5b62480209aae4f096a642c8600c
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-evs 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.

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