Skip to main content

Getting Started

Installation

pip install capo-migration-hub-refactor-spaces

Usage

from capo_migration_hub_refactor_spaces import AsyncMigrationHubRefactorSpacesClient


async def main():
    async with AsyncMigrationHubRefactorSpacesClient() as migration_hub_refactor_spaces:
        # Example: call the create_application operation
        response = await migration_hub_refactor_spaces.create_application()
        print(response["name"])

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_migration_hub_refactor_spaces import AsyncMigrationHubRefactorSpacesClient


async def main():
    async with AsyncMigrationHubRefactorSpacesClient() as migration_hub_refactor_spaces:
        # Example: paginate over list_applications
        async for item in migration_hub_refactor_spaces.iter_list_applications():
            print(item)

Error Handling

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

from capo_migration_hub_refactor_spaces import AsyncMigrationHubRefactorSpacesClient
from capo_migration_hub_refactor_spaces.error import AccessDeniedException


async def main():
    async with AsyncMigrationHubRefactorSpacesClient() as migration_hub_refactor_spaces:
        try:
            await migration_hub_refactor_spaces.create_application()
        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_migration_hub_refactor_spaces import AsyncMigrationHubRefactorSpacesClient


async def main():
    async with AsyncMigrationHubRefactorSpacesClient() as migration_hub_refactor_spaces:
        # Default: 3 attempts for every operation
        response = await migration_hub_refactor_spaces.create_application()

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

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

Metadata

Release files for capo-migration-hub-refactor-spaces 0.3.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-migration-hub-refactor-spaces 0.3.0
File Size Uploaded Provenance
capo_migration_hub_refactor_spaces-0.3.0.tar.gz 98.5 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-migration-hub-refactor-spaces 0.3.0
File Interpreter ABI Platform
capo_migration_hub_refactor_spaces-0.3.0-py3-none-any.whl Python 3 none any Details

Total release size: 311.9 kB

Release files / capo_migration_hub_refactor_spaces-0.3.0.tar.gz

Download URL capo_migration_hub_refactor_spaces-0.3.0.tar.gz
Size 98.5 kB
Tags Source
SHA-256 checksum
How to use checksums
cd45ed9093d79be8af5ad79d2a38af15deddc93be608769cf244f70c2a5b3ad5
BLAKE2b-256 checksum
How to use checksums
f9392939efd182986391131f955c8142e83c4e3650beb016bd4d64a83c445d1d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.22 {"installer":{"name":"uv","version":"0.12.22","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_migration_hub_refactor_spaces-0.3.0-py3-none-any.whl

Download URL capo_migration_hub_refactor_spaces-0.3.0-py3-none-any.whl
Size 213.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
6b4574eb5e1ef904d6269d5998fd833bd31c280b680c42881d03cd98381c162b
BLAKE2b-256 checksum
How to use checksums
87d930cc0b1c5ceb8005e8009ca72d6ea909803a550be62aa7641c224620d7e2
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.22 {"installer":{"name":"uv","version":"0.12.22","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-migration-hub-refactor-spaces 0.3.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