Getting Started
Installation
pip install capo-amplifybackend
Usage
from capo_amplifybackend import AsyncAmplifyBackendClient
async def main():
async with AsyncAmplifyBackendClient() as amplify_backend:
# Example: call the clone_backend operation
response = await amplify_backend.clone_backend()
print(response["app_id"])
Error Handling
The SDK raises exceptions for errors returned by the API. Catch them to handle failures gracefully.
from capo_amplifybackend import AsyncAmplifyBackendClient
from capo_amplifybackend.error import BadRequestException
async def main():
async with AsyncAmplifyBackendClient() as amplify_backend:
try:
await amplify_backend.clone_backend()
except BadRequestException 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_amplifybackend import AsyncAmplifyBackendClient
async def main():
async with AsyncAmplifyBackendClient() as amplify_backend:
# Default: 3 attempts for every operation
response = await amplify_backend.clone_backend()
# Override per operation
response = await amplify_backend.clone_backend(config_overrides={"retry_max_attempts": 5})
# Disable retries for this call
response = await amplify_backend.clone_backend(config_overrides={"retry_max_attempts": 1})
Metadata
Release files for capo-amplifybackend 0.5.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_amplifybackend-0.5.0.tar.gz | 91.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| capo_amplifybackend-0.5.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 306.7 kB
Release files / capo_amplifybackend-0.5.0.tar.gz
| Download URL | capo_amplifybackend-0.5.0.tar.gz |
|---|---|
| Size | 91.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
428915dc0a61c0c2e656f9e063bc5e3c4138892acbd34db24882af2f0f1fd4e2
|
|
BLAKE2b-256 checksum How to use checksums |
5878c6a369906e7afff8dfb409cf29b8da1803e4df4fef1a3485aa8de5116a54
|
| 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_amplifybackend-0.5.0-py3-none-any.whl
| Download URL | capo_amplifybackend-0.5.0-py3-none-any.whl |
|---|---|
| Size | 215.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b81aeafc1724adc48e780454e6bb172f09a9a242c78a020fcfc3dabaecfff461
|
|
BLAKE2b-256 checksum How to use checksums |
f36e70159728b004003a8b393cae595ef83b1254d869bc79b743059b498e4be9
|
| 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-amplifybackend 0.5.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.