Skip to main content

Getting Started

Installation

pip install capo-neptune-graph

Usage

from capo_neptune_graph import AsyncNeptuneGraphClient


async def main():
    async with AsyncNeptuneGraphClient() as neptune_graph:
        # Example: call the cancel_query operation
        response = await neptune_graph.cancel_query()
        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_neptune_graph import AsyncNeptuneGraphClient


async def main():
    async with AsyncNeptuneGraphClient() as neptune_graph:
        # Example: paginate over list_graphs
        async for item in neptune_graph.iter_list_graphs():
            print(item)

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_neptune_graph import AsyncNeptuneGraphClient


async def main():
    async with AsyncNeptuneGraphClient() as neptune_graph:
        # Example: call execute_query and read the streaming response
        async with neptune_graph.execute_query() as response:
            async for chunk in response["payload"]:
                print(chunk)

Error Handling

The SDK raises exceptions for errors returned by the API. Catch them to handle failures gracefully.

from capo_neptune_graph import AsyncNeptuneGraphClient
from capo_neptune_graph.error import AccessDeniedException


async def main():
    async with AsyncNeptuneGraphClient() as neptune_graph:
        try:
            await neptune_graph.cancel_query()
        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_neptune_graph import AsyncNeptuneGraphClient


async def main():
    async with AsyncNeptuneGraphClient() as neptune_graph:
        # Default: 3 attempts for every operation
        response = await neptune_graph.cancel_query()

        # Override per operation
        response = await neptune_graph.cancel_query(config_overrides={"retry_max_attempts": 5})

        # Disable retries for this call
        response = await neptune_graph.cancel_query(config_overrides={"retry_max_attempts": 1})

Metadata

Release files for capo-neptune-graph 0.4.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for capo-neptune-graph 0.4.0
File Size Uploaded Provenance
capo_neptune_graph-0.4.0.tar.gz 131.9 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-neptune-graph 0.4.0
File Interpreter ABI Platform
capo_neptune_graph-0.4.0-py3-none-any.whl Python 3 none any Details

Total release size: 407.2 kB

Release files / capo_neptune_graph-0.4.0.tar.gz

Download URL capo_neptune_graph-0.4.0.tar.gz
Size 131.9 kB
Tags Source
SHA-256 checksum
How to use checksums
f3c07727ba42f3ddacdf0ca2ca7fdb6cd4fd0dd480a89821a00f68e8b9073e34
BLAKE2b-256 checksum
How to use checksums
febee3d2a5168af9f928fcf51d8706fcc23dff7d80a164354da255215eeae2d8
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.23 {"installer":{"name":"uv","version":"0.12.23","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_neptune_graph-0.4.0-py3-none-any.whl

Download URL capo_neptune_graph-0.4.0-py3-none-any.whl
Size 275.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
6c3b3fe5c973cbdb61754e3f535ffd663f1370adc97b7d4ef3c9565294c7cf58
BLAKE2b-256 checksum
How to use checksums
2a1d4c7aba2a80275e4b611681db586fef73c5f74091f445814a843ea063f334
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.23 {"installer":{"name":"uv","version":"0.12.23","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-neptune-graph 0.4.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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page