Skip to main content

Getting Started

Installation

pip install capo-s3vectors

Usage

from capo_s3vectors import AsyncS3VectorsClient


async def main():
    async with AsyncS3VectorsClient() as s3_vectors:
        # Example: call the list_tags_for_resource operation
        response = await s3_vectors.list_tags_for_resource()
        print(response["tags"])

Error Handling

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

from capo_s3vectors import AsyncS3VectorsClient
from capo_s3vectors.error import AccessDeniedException


async def main():
    async with AsyncS3VectorsClient() as s3_vectors:
        try:
            await s3_vectors.list_tags_for_resource()
        except AccessDeniedException 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_s3vectors import AsyncS3VectorsClient


async def main():
    async with AsyncS3VectorsClient() as s3_vectors:
        # Default: 3 attempts for every operation
        response = await s3_vectors.list_tags_for_resource()

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

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

Metadata

Release files for capo-s3vectors 0.1.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-s3vectors 0.1.0
File Size Uploaded Provenance
capo_s3vectors-0.1.0.tar.gz 69.2 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-s3vectors 0.1.0
File Interpreter ABI Platform
capo_s3vectors-0.1.0-py3-none-any.whl Python 3 none any Details

Total release size: 222.5 kB

Release files / capo_s3vectors-0.1.0.tar.gz

Download URL capo_s3vectors-0.1.0.tar.gz
Size 69.2 kB
Tags Source
SHA-256 checksum
How to use checksums
c1ebc5984a0c4c75ae92ce0606fdb553310e588c37917aeee6d85f041247b9e0
BLAKE2b-256 checksum
How to use checksums
1eeae2e939bbd3bf0f09f4e812c09c1360df35f7ec3bf162efc6e32885ec7bbd
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.20 {"installer":{"name":"uv","version":"0.12.20","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_s3vectors-0.1.0-py3-none-any.whl

Download URL capo_s3vectors-0.1.0-py3-none-any.whl
Size 153.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
9701d5d6549e8dc668038c5c941db56de8168ffb70425dd7db0075368cc2d710
BLAKE2b-256 checksum
How to use checksums
764cb48c3e5de51de3d8832458ad3a24cc7f582c6d9dc0953bd6b56feaf46e45
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.20 {"installer":{"name":"uv","version":"0.12.20","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-s3vectors 0.1.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