Getting Started
Installation
pip install capo-workmailmessageflow
Usage
from capo_workmailmessageflow import AsyncWorkMailMessageFlowClient
async def main():
async with AsyncWorkMailMessageFlowClient() as work_mail_message_flow:
# Example: call the get_raw_message_content operation
response = await work_mail_message_flow.get_raw_message_content()
print(response["message_content"])
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_workmailmessageflow import AsyncWorkMailMessageFlowClient
async def main():
async with AsyncWorkMailMessageFlowClient() as work_mail_message_flow:
# Example: call get_raw_message_content and read the streaming response
async with work_mail_message_flow.get_raw_message_content() as response:
async for chunk in response["message_content"]:
print(chunk)
Error Handling
The SDK raises exceptions for errors returned by the API. Catch them to handle failures gracefully.
from capo_workmailmessageflow import AsyncWorkMailMessageFlowClient
from capo_workmailmessageflow.error import ResourceNotFoundException
async def main():
async with AsyncWorkMailMessageFlowClient() as work_mail_message_flow:
try:
await work_mail_message_flow.get_raw_message_content()
except ResourceNotFoundException 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_workmailmessageflow import AsyncWorkMailMessageFlowClient
async def main():
async with AsyncWorkMailMessageFlowClient() as work_mail_message_flow:
# Default: 3 attempts for every operation
response = await work_mail_message_flow.get_raw_message_content()
# Override per operation
response = await work_mail_message_flow.get_raw_message_content(config_overrides={"retry_max_attempts": 5})
# Disable retries for this call
response = await work_mail_message_flow.get_raw_message_content(config_overrides={"retry_max_attempts": 1})
Metadata
Release files for capo-workmailmessageflow 0.8.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_workmailmessageflow-0.8.0.tar.gz | 57.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| capo_workmailmessageflow-0.8.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 126.7 kB
Release files / capo_workmailmessageflow-0.8.0.tar.gz
| Download URL | capo_workmailmessageflow-0.8.0.tar.gz |
|---|---|
| Size | 57.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
757828a76677ca7794ea4cb54901a43cc934bfa3d5cf8724b072b3a54926f872
|
|
BLAKE2b-256 checksum How to use checksums |
9c53357edf4fc9b72e52cc4a140db54ad22dae6eb9748b56062e95796e9abb43
|
| 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_workmailmessageflow-0.8.0-py3-none-any.whl
| Download URL | capo_workmailmessageflow-0.8.0-py3-none-any.whl |
|---|---|
| Size | 69.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ca25f0360b32dbeee2620fe2a4ddc17a0f2c04ed34efb95819fa83695bca0e94
|
|
BLAKE2b-256 checksum How to use checksums |
2f59ccd33e1602de194b9f9a398564b6f5258e0bf17909bbad2f018a5d2e355c
|
| 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-workmailmessageflow 0.8.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.