Getting Started
Installation
pip install capo-amp
Usage
from capo_amp import AsyncampClient
async def main():
async with AsyncampClient() as amp:
# Example: call the get_default_scraper_configuration operation
response = await amp.get_default_scraper_configuration()
print(response["configuration"])
Error Handling
The SDK raises exceptions for errors returned by the API. Catch them to handle failures gracefully.
from capo_amp import AsyncampClient
from capo_amp.error import AccessDeniedException
async def main():
async with AsyncampClient() as amp:
try:
await amp.get_default_scraper_configuration()
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_amp import AsyncampClient
async def main():
async with AsyncampClient() as amp:
# Default: 3 attempts for every operation
response = await amp.get_default_scraper_configuration()
# Override per operation
response = await amp.get_default_scraper_configuration(config_overrides={"retry_max_attempts": 5})
# Disable retries for this call
response = await amp.get_default_scraper_configuration(config_overrides={"retry_max_attempts": 1})
Metadata
Release files for capo-amp 0.1.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_amp-0.1.0.tar.gz | 96.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| capo_amp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 363.1 kB
Release files / capo_amp-0.1.0.tar.gz
| Download URL | capo_amp-0.1.0.tar.gz |
|---|---|
| Size | 96.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ae6542a7d611556b952f1a9f72aa548c7eff4acebf47140bb8106f06580d4fba
|
|
BLAKE2b-256 checksum How to use checksums |
446d2e78f514f91b67d3d8a91a25e1e2effc8d9c7bad348e86d293405492736a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.14 {"installer":{"name":"uv","version":"0.12.14","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_amp-0.1.0-py3-none-any.whl
| Download URL | capo_amp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 267.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
faa5a56e82418a69b221636013c986d3e038b33d4c30803f91d5097ca6235fd9
|
|
BLAKE2b-256 checksum How to use checksums |
c06cea16fab9bc128fb19a092056045c2245aa9195f8f16db520f9e1519dd38e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.14 {"installer":{"name":"uv","version":"0.12.14","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-amp 0.1.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.