Skip to main content

Getting Started

Installation

pip install capo-codecommit

Usage

from capo_codecommit import AsyncCodeCommitClient


async def main():
    async with AsyncCodeCommitClient() as code_commit:
        # Example: call the associate_approval_rule_template_with_repository operation
        response = await code_commit.associate_approval_rule_template_with_repository()
        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_codecommit import AsyncCodeCommitClient


async def main():
    async with AsyncCodeCommitClient() as code_commit:
        # Example: paginate over describe_merge_conflicts
        async for item in code_commit.iter_describe_merge_conflicts():
            print(item)

Error Handling

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

from capo_codecommit import AsyncCodeCommitClient
from capo_codecommit.error import ApprovalRuleTemplateDoesNotExistException


async def main():
    async with AsyncCodeCommitClient() as code_commit:
        try:
            await code_commit.associate_approval_rule_template_with_repository()
        except ApprovalRuleTemplateDoesNotExistException 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_codecommit import AsyncCodeCommitClient


async def main():
    async with AsyncCodeCommitClient() as code_commit:
        # Default: 3 attempts for every operation
        response = await code_commit.associate_approval_rule_template_with_repository()

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

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

Metadata

Release files for capo-codecommit 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-codecommit 0.3.0
File Size Uploaded Provenance
capo_codecommit-0.3.0.tar.gz 261.9 kB Without provenance Details

Built distribution (wheel)

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

Total release size: 988.4 kB

Release files / capo_codecommit-0.3.0.tar.gz

Download URL capo_codecommit-0.3.0.tar.gz
Size 261.9 kB
Tags Source
SHA-256 checksum
How to use checksums
c4e916d019e9a7a14fcecf619f5ba9c2a17e288ab87bde3fc7b00a0c09e17e8d
BLAKE2b-256 checksum
How to use checksums
82b794c64925a2b043b8e8857ea0431657898b5c1814ac8161712bee29d6cac4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.18 {"installer":{"name":"uv","version":"0.12.18","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_codecommit-0.3.0-py3-none-any.whl

Download URL capo_codecommit-0.3.0-py3-none-any.whl
Size 726.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
ac7dc38d7fad54910c1d34eb639ef0863a1dc48e3d4664e94d4147f299b1e642
BLAKE2b-256 checksum
How to use checksums
fc8b0f75819133d1aea56124027a5ef4df0a5f851208703adfa7fc742d66caaa
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.18 {"installer":{"name":"uv","version":"0.12.18","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-codecommit 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