Skip to main content

Getting Started

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.8.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.8.0
File Size Uploaded Provenance
capo_workdocs-0.8.0.tar.gz 139.0 kB Without provenance Details

Built distribution (wheel)

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

Total release size: 471.1 kB

Release files / capo_workdocs-0.8.0.tar.gz

Download URL capo_workdocs-0.8.0.tar.gz
Size 139.0 kB
Tags Source
SHA-256 checksum
How to use checksums
36f417a15fa78cbed3008ca0865fba40bcd4ed138a66192c2bcfdd8a6023ce0a
BLAKE2b-256 checksum
How to use checksums
1036037511923e799ab72082ff65d2c77eeae10fde4d85c5958a2ab7a6b57106
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_workdocs-0.8.0-py3-none-any.whl

Download URL capo_workdocs-0.8.0-py3-none-any.whl
Size 332.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
996a3eba9fe70019d79a8aca5cfefda796fde84fb75cbcd0178990935e474acc
BLAKE2b-256 checksum
How to use checksums
ed3267bd822b37f2e4599065580fbd117dfb3b6053a57c6ff4c9c2f512e166f1
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-workdocs 0.8.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