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.4.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.4.0
File Size Uploaded Provenance
capo_sagemakerjobruntime-0.4.0.tar.gz 57.3 kB Without provenance Details

Built distribution (wheel)

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

Total release size: 134.3 kB

Release files / capo_sagemakerjobruntime-0.4.0.tar.gz

Download URL capo_sagemakerjobruntime-0.4.0.tar.gz
Size 57.3 kB
Tags Source
SHA-256 checksum
How to use checksums
311fb7c328d7bd449533d19870eba02ade06825ea76be22915cbb0605f7cddeb
BLAKE2b-256 checksum
How to use checksums
d7adf4222c2095869c9a16baa5d45c48afb888f34607295a4830e83e848072b8
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.0 {"installer":{"name":"uv","version":"0.13.0","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.4.0-py3-none-any.whl

Download URL capo_sagemakerjobruntime-0.4.0-py3-none-any.whl
Size 77.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
300623d1f424c5a463134299aa0c3be149ae974ac234e8a1c1d31d272c3757ee
BLAKE2b-256 checksum
How to use checksums
1b216266dd3161c0fd4ea68095928a4b896fd1c495c66214004d8ef3deceee4f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.0 {"installer":{"name":"uv","version":"0.13.0","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.4.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