Skip to main content

Getting Started

Installation

pip install capo-partnercentral-selling

Usage

from capo_partnercentral_selling import AsyncPartnerCentralSellingClient


async def main():
    async with AsyncPartnerCentralSellingClient() as partner_central_selling:
        # Example: call the create_engagement_context operation
        response = await partner_central_selling.create_engagement_context()
        print(response["engagement_id"])

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_partnercentral_selling import AsyncPartnerCentralSellingClient


async def main():
    async with AsyncPartnerCentralSellingClient() as partner_central_selling:
        # Example: paginate over list_engagements
        async for item in partner_central_selling.iter_list_engagements():
            print(item)

Error Handling

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

from capo_partnercentral_selling import AsyncPartnerCentralSellingClient
from capo_partnercentral_selling.error import AccessDeniedException


async def main():
    async with AsyncPartnerCentralSellingClient() as partner_central_selling:
        try:
            await partner_central_selling.create_engagement_context()
        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_partnercentral_selling import AsyncPartnerCentralSellingClient


async def main():
    async with AsyncPartnerCentralSellingClient() as partner_central_selling:
        # Default: 3 attempts for every operation
        response = await partner_central_selling.create_engagement_context()

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

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

Metadata

Release files for capo-partnercentral-selling 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-partnercentral-selling 0.8.0
File Size Uploaded Provenance
capo_partnercentral_selling-0.8.0.tar.gz 281.6 kB Without provenance Details

Built distribution (wheel)

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

Total release size: 867.1 kB

Release files / capo_partnercentral_selling-0.8.0.tar.gz

Download URL capo_partnercentral_selling-0.8.0.tar.gz
Size 281.6 kB
Tags Source
SHA-256 checksum
How to use checksums
a98cb6007b384702d180240aa5e7d6cdd56e090100caa6724b725fd52d6a14c9
BLAKE2b-256 checksum
How to use checksums
d08916d74c7a5fc3e3ce5d81a881a6557d6aaf1d3c985a6465c4ab9b2c0438d3
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_partnercentral_selling-0.8.0-py3-none-any.whl

Download URL capo_partnercentral_selling-0.8.0-py3-none-any.whl
Size 585.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
80edf0d05280450f25af85c0f6503c43060329bafe38c7c818da2f17ed8a9619
BLAKE2b-256 checksum
How to use checksums
c7ce55b1260f0cbc034651a022362be8d639107fa0fe11b421d35382b6b9a54d
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-partnercentral-selling 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.

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