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.2.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.2.0
File Size Uploaded Provenance
capo_codecommit-0.2.0.tar.gz 258.6 kB Without provenance Details

Built distribution (wheel)

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

Total release size: 983.0 kB

Release files / capo_codecommit-0.2.0.tar.gz

Download URL capo_codecommit-0.2.0.tar.gz
Size 258.6 kB
Tags Source
SHA-256 checksum
How to use checksums
024e1591681f3ce76794b6c0726a794c387bdfce24469037ae28914bbd0399bb
BLAKE2b-256 checksum
How to use checksums
95aa9fa1b4c1f4a43fa70e5ea7eb574eec20e7a2c49429ac25cca4f93654a8e5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.17 {"installer":{"name":"uv","version":"0.12.17","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.2.0-py3-none-any.whl

Download URL capo_codecommit-0.2.0-py3-none-any.whl
Size 724.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
05b82b670469f53ddbbb2a94cf4bc1308a6a7b4db53ed1b2258cc0a0af2fbd7a
BLAKE2b-256 checksum
How to use checksums
62b5be69b1b1940954c4cac37a112a8489fbe427e0a75ebd4300ccb504ce7bf7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.17 {"installer":{"name":"uv","version":"0.12.17","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.2.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