Skip to main content

capo-taxsettings: typed, async Python SDK for AWS Taxsettings

capo-taxsettings is a typed Python SDK for AWS Taxsettings. It has an async client, AsyncTaxSettingsClient, for asyncio and trio, and a sync client, TaxSettingsClient, with the same methods. Requests and responses are typed with TypedDicts, so your editor and type checker know every field.

It is part of capo, a community-driven alternative to boto3 and aioboto3, built on its own HTTP stack instead of botocore and generated from the official AWS Smithy models. Documentation: https://capo-sdk.dev/services/taxsettings/

Installation

pip install capo-taxsettings

Usage

from capo_taxsettings import AsyncTaxSettingsClient


async def main():
    async with AsyncTaxSettingsClient() as tax_settings:
        # Example: call the batch_delete_tax_registration operation
        response = await tax_settings.batch_delete_tax_registration()
        print(response["errors"])

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_taxsettings import AsyncTaxSettingsClient


async def main():
    async with AsyncTaxSettingsClient() as tax_settings:
        # Example: paginate over list_supplemental_tax_registrations
        async for item in tax_settings.iter_list_supplemental_tax_registrations():
            print(item)

Error Handling

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

from capo_taxsettings import AsyncTaxSettingsClient
from capo_taxsettings.error import ConflictException


async def main():
    async with AsyncTaxSettingsClient() as tax_settings:
        try:
            await tax_settings.batch_delete_tax_registration()
        except ConflictException 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_taxsettings import AsyncTaxSettingsClient


async def main():
    async with AsyncTaxSettingsClient() as tax_settings:
        # Default: 3 attempts for every operation
        response = await tax_settings.batch_delete_tax_registration()

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

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

Metadata

Release files for capo-taxsettings 0.9.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-taxsettings 0.9.0
File Size Uploaded Provenance
capo_taxsettings-0.9.0.tar.gz 109.0 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-taxsettings 0.9.0
File Interpreter ABI Platform
capo_taxsettings-0.9.0-py3-none-any.whl Python 3 none any Details

Total release size: 327.9 kB

Release files / capo_taxsettings-0.9.0.tar.gz

Download URL capo_taxsettings-0.9.0.tar.gz
Size 109.0 kB
Tags Source
SHA-256 checksum
How to use checksums
bff8971c75b0297d1c1944ee18b93e00045bb7722d928f7b45518af34874edb2
BLAKE2b-256 checksum
How to use checksums
61f4144f1835a9602536c826d1fe16e3898accb80da64cdff718e6b1fa92680e
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_taxsettings-0.9.0-py3-none-any.whl

Download URL capo_taxsettings-0.9.0-py3-none-any.whl
Size 218.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
5977ea08a92e47c0a25a9f88014bb152fa34a5746c3c117c49fe1265750f13cf
BLAKE2b-256 checksum
How to use checksums
8ffd83c168a807bcc6f4d917d6449219d2e40fc724b27fa02c402c6cd110adee
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-taxsettings 0.9.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