Skip to main content

Getting Started

Installation

pip install capo-qconnect

Usage

from capo_qconnect import AsyncQConnectClient


async def main():
    async with AsyncQConnectClient() as q_connect:
        # Example: call the list_tags_for_resource operation
        response = await q_connect.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_qconnect import AsyncQConnectClient
from capo_qconnect.error import ResourceNotFoundException


async def main():
    async with AsyncQConnectClient() as q_connect:
        try:
            await q_connect.list_tags_for_resource()
        except ResourceNotFoundException 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_qconnect import AsyncQConnectClient


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

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

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

Metadata

Release files for capo-qconnect 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-qconnect 0.1.0
File Size Uploaded Provenance
capo_qconnect-0.1.0.tar.gz 221.9 kB Without provenance Details

Built distribution (wheel)

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

Total release size: 930.4 kB

Release files / capo_qconnect-0.1.0.tar.gz

Download URL capo_qconnect-0.1.0.tar.gz
Size 221.9 kB
Tags Source
SHA-256 checksum
How to use checksums
4a3bf8413ef55c30050e9367e3827e60762ffbf86e3ad4fc28b21c73ab53cd8c
BLAKE2b-256 checksum
How to use checksums
ea4fa198b9085335f00c3c5a8f803c6fd621bc3110deddff1fca32917bf79a56
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.19 {"installer":{"name":"uv","version":"0.12.19","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_qconnect-0.1.0-py3-none-any.whl

Download URL capo_qconnect-0.1.0-py3-none-any.whl
Size 708.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
3af4b625e5f8862a0f5195f6b69c0de5769c22613e8ebc6db4e5e6ac7fa33edd
BLAKE2b-256 checksum
How to use checksums
097ac50269f49c64e8c071b5f999ac9e72bdbf052515c57959584ff3b9c53af7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.19 {"installer":{"name":"uv","version":"0.12.19","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-qconnect 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