Getting Started
Installation
pip install capo-macie2
Usage
from capo_macie2 import AsyncMacie2Client
async def main():
async with AsyncMacie2Client() as macie2:
# Example: call the accept_invitation operation
response = await macie2.accept_invitation()
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_macie2 import AsyncMacie2Client
async def main():
async with AsyncMacie2Client() as macie2:
# Example: paginate over describe_buckets
async for item in macie2.iter_describe_buckets():
print(item)
Error Handling
The SDK raises exceptions for errors returned by the API. Catch them to handle failures gracefully.
from capo_macie2 import AsyncMacie2Client
from capo_macie2.error import AccessDeniedException
async def main():
async with AsyncMacie2Client() as macie2:
try:
await macie2.accept_invitation()
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_macie2 import AsyncMacie2Client
async def main():
async with AsyncMacie2Client() as macie2:
# Default: 3 attempts for every operation
response = await macie2.accept_invitation()
# Override per operation
response = await macie2.accept_invitation(config_overrides={"retry_max_attempts": 5})
# Disable retries for this call
response = await macie2.accept_invitation(config_overrides={"retry_max_attempts": 1})
Metadata
Release files for capo-macie2 0.3.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_macie2-0.3.0.tar.gz | 228.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| capo_macie2-0.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 814.7 kB
Release files / capo_macie2-0.3.0.tar.gz
| Download URL | capo_macie2-0.3.0.tar.gz |
|---|---|
| Size | 228.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
476e5e77c1e69f5a1c78dc11a4214195df4be8d0abd8707ece93a8e85d6338b8
|
|
BLAKE2b-256 checksum How to use checksums |
348c3d084693729785c2999b85b66f5581fba3ea6905b42d03325cdabcaa8c1d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.22 {"installer":{"name":"uv","version":"0.12.22","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_macie2-0.3.0-py3-none-any.whl
| Download URL | capo_macie2-0.3.0-py3-none-any.whl |
|---|---|
| Size | 586.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d52bded029112fc8aab8e211f7f7666615600371111da06815e7914f25d79e11
|
|
BLAKE2b-256 checksum How to use checksums |
8f3a27c9f3fc81fc02d7c618198445fdbef0619c3c8d1f7381ef6ccb6eca4c26
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.22 {"installer":{"name":"uv","version":"0.12.22","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-macie2 0.3.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.