Getting Started
Installation
pip install capo-sagemaker-metrics
Usage
from capo_sagemaker_metrics import AsyncSageMakerMetricsClient
async def main():
async with AsyncSageMakerMetricsClient() as sage_maker_metrics:
# Example: call the batch_get_metrics operation
response = await sage_maker_metrics.batch_get_metrics()
print(response["metric_query_results"])
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_sagemaker_metrics import AsyncSageMakerMetricsClient
async def main():
async with AsyncSageMakerMetricsClient() as sage_maker_metrics:
# Default: 3 attempts for every operation
response = await sage_maker_metrics.batch_get_metrics()
# Override per operation
response = await sage_maker_metrics.batch_get_metrics(config_overrides={"retry_max_attempts": 5})
# Disable retries for this call
response = await sage_maker_metrics.batch_get_metrics(config_overrides={"retry_max_attempts": 1})
Metadata
Release files for capo-sagemaker-metrics 0.7.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| capo_sagemaker_metrics-0.7.0.tar.gz | 58.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| capo_sagemaker_metrics-0.7.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 131.1 kB
Release files / capo_sagemaker_metrics-0.7.0.tar.gz
| Download URL | capo_sagemaker_metrics-0.7.0.tar.gz |
|---|---|
| Size | 58.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
89aebf59645bddd30af216b3f0b89e7e48bff8a0de8bdab2ea8bbde31938a364
|
|
BLAKE2b-256 checksum How to use checksums |
eb90d5603e8022d8cda3d54a9a3dd87673e8c942ceb4af83f4ddc84045d9f99b
|
| 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_sagemaker_metrics-0.7.0-py3-none-any.whl
| Download URL | capo_sagemaker_metrics-0.7.0-py3-none-any.whl |
|---|---|
| Size | 72.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
db48a40b45db85c48e1aa1663f80202e2365b8491fcc62b8bb6e365f5d32748c
|
|
BLAKE2b-256 checksum How to use checksums |
56cd56c4988aa0be9e4640e8ba45da903c86313496f51bf52fdc27121efc2573
|
| 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-sagemaker-metrics 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.