Skip to main content

capo-workdocs: typed, async Python SDK for AWS Workdocs

capo-workdocs is a typed Python SDK for AWS Workdocs. It has an async client, AsyncWorkDocsClient, for asyncio and trio, and a sync client, WorkDocsClient, 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/workdocs/

Installation

pip install capo-workdocs

Usage

from capo_workdocs import AsyncWorkDocsClient


async def main():
    async with AsyncWorkDocsClient() as work_docs:
        # Example: call the abort_document_version_upload operation
        response = await work_docs.abort_document_version_upload()
        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_workdocs import AsyncWorkDocsClient


async def main():
    async with AsyncWorkDocsClient() as work_docs:
        # Example: paginate over describe_activities
        async for item in work_docs.iter_describe_activities():
            print(item)

Error Handling

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

from capo_workdocs import AsyncWorkDocsClient
from capo_workdocs.error import ConcurrentModificationException


async def main():
    async with AsyncWorkDocsClient() as work_docs:
        try:
            await work_docs.abort_document_version_upload()
        except ConcurrentModificationException 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_workdocs import AsyncWorkDocsClient


async def main():
    async with AsyncWorkDocsClient() as work_docs:
        # Default: 3 attempts for every operation
        response = await work_docs.abort_document_version_upload()

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

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

Metadata

Release files for capo-workdocs 0.10.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-workdocs 0.10.0
File Size Uploaded Provenance
capo_workdocs-0.10.0.tar.gz 140.0 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-workdocs 0.10.0
File Interpreter ABI Platform
capo_workdocs-0.10.0-py3-none-any.whl Python 3 none any Details

Total release size: 472.8 kB

Release files / capo_workdocs-0.10.0.tar.gz

Download URL capo_workdocs-0.10.0.tar.gz
Size 140.0 kB
Tags Source
SHA-256 checksum
How to use checksums
2cbd09392cd41ce7bdee8ec9cdad960e640bed85b91e918e6f14e6c64788f1d8
BLAKE2b-256 checksum
How to use checksums
9784ff8945af50470166cdb9f4562b7d3cd151a1d320d46fe1c2860827c18655
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.5 {"installer":{"name":"uv","version":"0.13.5","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_workdocs-0.10.0-py3-none-any.whl

Download URL capo_workdocs-0.10.0-py3-none-any.whl
Size 332.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
292fb9d4240e2780f205f206e5b2eaa8745157dd5ade7ab32eec357f97ddf2ca
BLAKE2b-256 checksum
How to use checksums
6319a0296e1182e255ee048bd218fe8373b255396ec11d63e728b611995193c4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.5 {"installer":{"name":"uv","version":"0.13.5","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-workdocs 0.10.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