Getting Started
Installation
pip install capo-neptunedata
Usage
from capo_neptunedata import AsyncneptunedataClient
async def main():
async with AsyncneptunedataClient() as neptunedata:
# Example: call the cancel_gremlin_query operation
response = await neptunedata.cancel_gremlin_query()
print(response["status"])
Error Handling
The SDK raises exceptions for errors returned by the API. Catch them to handle failures gracefully.
from capo_neptunedata import AsyncneptunedataClient
from capo_neptunedata.error import BadRequestException
async def main():
async with AsyncneptunedataClient() as neptunedata:
try:
await neptunedata.cancel_gremlin_query()
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_neptunedata import AsyncneptunedataClient
async def main():
async with AsyncneptunedataClient() as neptunedata:
# Default: 3 attempts for every operation
response = await neptunedata.cancel_gremlin_query()
# Override per operation
response = await neptunedata.cancel_gremlin_query(config_overrides={"retry_max_attempts": 5})
# Disable retries for this call
response = await neptunedata.cancel_gremlin_query(config_overrides={"retry_max_attempts": 1})
Metadata
Release files for capo-neptunedata 0.7.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_neptunedata-0.7.0.tar.gz | 149.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| capo_neptunedata-0.7.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 478.6 kB
Release files / capo_neptunedata-0.7.0.tar.gz
| Download URL | capo_neptunedata-0.7.0.tar.gz |
|---|---|
| Size | 149.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
775c90b989ec2c67faa06fa09d27746970652296b161c7d1fca356aae2ec0a89
|
|
BLAKE2b-256 checksum How to use checksums |
8f5777876b5c8cd34ff6ed7065fc7f8010794e3757858c8c5bbc3c5683734fbd
|
| 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_neptunedata-0.7.0-py3-none-any.whl
| Download URL | capo_neptunedata-0.7.0-py3-none-any.whl |
|---|---|
| Size | 329.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1e4e777a51b0f66eea5833d1370f2fd5d7a25bbb921104ead27f02b8debbe049
|
|
BLAKE2b-256 checksum How to use checksums |
a926ca11c7917116f93f36248700c53f731fbc67886581d803e5571578194b21
|
| 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-neptunedata 0.7.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.