Skip to main content

Getting Started

Installation

pip install capo-sagemakerjobruntime

Usage

from capo_sagemakerjobruntime import AsyncSagemakerJobRuntimeClient


async def main():
    async with AsyncSagemakerJobRuntimeClient() as sagemaker_job_runtime:
        # Example: call the complete_rollout operation
        response = await sagemaker_job_runtime.complete_rollout()
        print(response)

Streaming Response

Some operations return a streaming response body. Use the operation as an async context manager and iterate over the response field to read chunks.

from capo_sagemakerjobruntime import AsyncSagemakerJobRuntimeClient


async def main():
    async with AsyncSagemakerJobRuntimeClient() as sagemaker_job_runtime:
        # Example: call sample_with_response_stream and read the streaming response
        async with sagemaker_job_runtime.sample_with_response_stream() as response:
            async for chunk in response["body"]:
                print(chunk)

Error Handling

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

from capo_sagemakerjobruntime import AsyncSagemakerJobRuntimeClient
from capo_sagemakerjobruntime.error import AccessDeniedException


async def main():
    async with AsyncSagemakerJobRuntimeClient() as sagemaker_job_runtime:
        try:
            await sagemaker_job_runtime.complete_rollout()
        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_sagemakerjobruntime import AsyncSagemakerJobRuntimeClient


async def main():
    async with AsyncSagemakerJobRuntimeClient() as sagemaker_job_runtime:
        # Default: 3 attempts for every operation
        response = await sagemaker_job_runtime.complete_rollout()

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

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

Metadata

Release files for capo-sagemakerjobruntime 0.7.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-sagemakerjobruntime 0.7.0
File Size Uploaded Provenance
capo_sagemakerjobruntime-0.7.0.tar.gz 60.7 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-sagemakerjobruntime 0.7.0
File Interpreter ABI Platform
capo_sagemakerjobruntime-0.7.0-py3-none-any.whl Python 3 none any Details

Total release size: 142.1 kB

Release files / capo_sagemakerjobruntime-0.7.0.tar.gz

Download URL capo_sagemakerjobruntime-0.7.0.tar.gz
Size 60.7 kB
Tags Source
SHA-256 checksum
How to use checksums
6545b3bde163a476d1538b1920b9dbbe8a66639adf510de66482e9178990dfe2
BLAKE2b-256 checksum
How to use checksums
551c1fdd78198e2ced157664fb102818e902aaccf3f9e16c4930787d3c50f659
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_sagemakerjobruntime-0.7.0-py3-none-any.whl

Download URL capo_sagemakerjobruntime-0.7.0-py3-none-any.whl
Size 81.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
2c1856c84ef39f715600ef8981210e2fff4c420ee3dae382f9f1ef81e9a0554c
BLAKE2b-256 checksum
How to use checksums
1f4ead6b37c2c275a7a8d7ba40e3e4541c4fd93c42082f241b2e2ccd471fb03e
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-sagemakerjobruntime 0.7.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