Skip to main content

Getting Started

Installation

pip install capo-workmail

Usage

from capo_workmail import AsyncWorkMailClient


async def main():
    async with AsyncWorkMailClient() as work_mail:
        # Example: call the associate_delegate_to_resource operation
        response = await work_mail.associate_delegate_to_resource()
        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_workmail import AsyncWorkMailClient


async def main():
    async with AsyncWorkMailClient() as work_mail:
        # Example: paginate over list_aliases
        async for item in work_mail.iter_list_aliases():
            print(item)

Error Handling

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

from capo_workmail import AsyncWorkMailClient
from capo_workmail.error import EntityNotFoundException


async def main():
    async with AsyncWorkMailClient() as work_mail:
        try:
            await work_mail.associate_delegate_to_resource()
        except EntityNotFoundException 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_workmail import AsyncWorkMailClient


async def main():
    async with AsyncWorkMailClient() as work_mail:
        # Default: 3 attempts for every operation
        response = await work_mail.associate_delegate_to_resource()

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

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

Metadata

Release files for capo-workmail 0.3.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-workmail 0.3.0
File Size Uploaded Provenance
capo_workmail-0.3.0.tar.gz 194.6 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-workmail 0.3.0
File Interpreter ABI Platform
capo_workmail-0.3.0-py3-none-any.whl Python 3 none any Details

Total release size: 725.2 kB

Release files / capo_workmail-0.3.0.tar.gz

Download URL capo_workmail-0.3.0.tar.gz
Size 194.6 kB
Tags Source
SHA-256 checksum
How to use checksums
0ae4b2b2c53b368803cb5c4f37d8db5a0d74f3db8552bcb27111d49ddf1029ef
BLAKE2b-256 checksum
How to use checksums
747dd4700a2ebda45b4f21dc7eee8f0a25ec89d48ded0ae628ac4c93bfa853fc
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.22 {"installer":{"name":"uv","version":"0.12.22","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_workmail-0.3.0-py3-none-any.whl

Download URL capo_workmail-0.3.0-py3-none-any.whl
Size 530.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
99c5bbfcc2a0badbcf27083e7134f8ed850dee2bbf957fd922224c3c3fb55451
BLAKE2b-256 checksum
How to use checksums
f79a27f25a1b4e3039fdf51685e13b80adac90f754efd10973c2ca66b4c17079
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.22 {"installer":{"name":"uv","version":"0.12.22","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-workmail 0.3.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