Getting Started
Installation
pip install capo-workspaces-instances
Usage
from capo_workspaces_instances import AsyncWorkspacesInstancesClient
async def main():
async with AsyncWorkspacesInstancesClient() as workspaces_instances:
# Example: call the associate_volume operation
response = await workspaces_instances.associate_volume()
print(response)
Pagination
Some operations in this SDK support pagination. If the operation supports pagination it will have an iter_ prefixed method that returns an async iterator.
from capo_workspaces_instances import AsyncWorkspacesInstancesClient
async def main():
async with AsyncWorkspacesInstancesClient() as workspaces_instances:
# Example: paginate over list_instance_types
async for item in workspaces_instances.iter_list_instance_types():
print(item)
Error Handling
The SDK raises exceptions for errors returned by the API. Catch them to handle failures gracefully.
from capo_workspaces_instances import AsyncWorkspacesInstancesClient
from capo_workspaces_instances.error import AccessDeniedException
async def main():
async with AsyncWorkspacesInstancesClient() as workspaces_instances:
try:
await workspaces_instances.associate_volume()
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_workspaces_instances import AsyncWorkspacesInstancesClient
async def main():
async with AsyncWorkspacesInstancesClient() as workspaces_instances:
# Default: 3 attempts for every operation
response = await workspaces_instances.associate_volume()
# Override per operation
response = await workspaces_instances.associate_volume(config_overrides={"retry_max_attempts": 5})
# Disable retries for this call
response = await workspaces_instances.associate_volume(config_overrides={"retry_max_attempts": 1})
Metadata
Release files for capo-workspaces-instances 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_workspaces_instances-0.1.0.tar.gz | 81.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| capo_workspaces_instances-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 254.4 kB
Release files / capo_workspaces_instances-0.1.0.tar.gz
| Download URL | capo_workspaces_instances-0.1.0.tar.gz |
|---|---|
| Size | 81.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
876ad2ca6ec95346cce649c559e02c86711ad39fd5c1939676d1368bb38ca3ba
|
|
BLAKE2b-256 checksum How to use checksums |
234d28f59fcf331d3f6801d45bad852954e6bb0e2724127dda15730f0218a1c5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.20 {"installer":{"name":"uv","version":"0.12.20","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_workspaces_instances-0.1.0-py3-none-any.whl
| Download URL | capo_workspaces_instances-0.1.0-py3-none-any.whl |
|---|---|
| Size | 172.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a5c9bf43aafb508f5b6a0586c60a904c900b4928c610208ba7c469f06558c378
|
|
BLAKE2b-256 checksum How to use checksums |
4074c24c3929f65c343134dbb7d07268e89f703e36822cae13b39f70a70bdbf0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.20 {"installer":{"name":"uv","version":"0.12.20","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-workspaces-instances 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.