Skip to main content

adbc-driver-hardcharger

The ADBC driver for Hardcharger™, GizmoData™'s DuckDB 2.0 server: a native Go driver (built on the Warp SQL ADBC driver) whose library ships in this wheel, with Python DB-API bindings. hardcharger:// URIs (port 31337 by default), query and session tags, hardcharger.* settings, browser sign-in, and an ADBC driver manifest so driver = "hardcharger" works in every ADBC language.

pip install adbc-driver-hardcharger     # this client
pip install hardcharger                 # the Hardcharger server, started from Python
pip install "hardcharger[adbc]"         # both
from adbc_driver_hardcharger import dbapi as hardcharger

with hardcharger.connect(uri="hardcharger://localhost?tls=false", username="hardcharger", password="change-me") as conn:
    with conn.cursor() as cur:
        cur.execute(operation="SELECT 42 AS answer, ? AS greeting", parameters=["hello"])
        print(cur.fetch_arrow_table())

hardcharger://host[:port] is HTTPS; ?tls=false is plain HTTP for development. See the repository README for tags, settings, browser sign-in, client certificate sign-in (auth_type="client_certificate"), token exchange with your identity provider's tokens (subject_token=), the TLS server name (tls_server_name=), reading the access token (conn.access_token, a bearer secret), attaching to an existing session (session_id=; with several replicas it works only when routing reaches the replica that holds the session), the driver manifest, and the C/C++ and Go examples.

Apache License 2.0. Built by GizmoData.

Connection profiles

Install the manifest with python -m adbc_driver_hardcharger.manifest, then reuse a standard ADBC TOML profile (driver = "hardcharger") with hardcharger.connect(profile="prod"), hardcharger.connect(uri="profile://prod"), or an absolute profile path. The generic adbc_driver_manager.dbapi.connect(profile="prod") uses the same file. See the profile setup and complete examples for search paths, environment-variable credentials, browser SSO and option overrides.

Metadata

Release files for adbc-driver-hardcharger 2.0.0

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

Built distributions (wheels)

Table of built distributions (wheels) for adbc-driver-hardcharger 2.0.0
File
adbc_driver_hardcharger-2.0.0-py3-none-win_amd64.whl Python 3 none Windows x86-64 Details
adbc_driver_hardcharger-2.0.0-py3-none-manylinux2014_aarch64.manylinux_2_17_aarch64.whl Python 3 none Linux glibc 2.17+ ARM64 Details
adbc_driver_hardcharger-2.0.0-py3-none-manylinux1_x86_64.manylinux_2_5_x86_64.whl Python 3 none Linux glibc 2.5+ x86-64 Details
adbc_driver_hardcharger-2.0.0-py3-none-macosx_11_0_x86_64.whl Python 3 none macOS 11.0+ x86-64 Details
adbc_driver_hardcharger-2.0.0-py3-none-macosx_11_0_arm64.whl Python 3 none macOS 11.0+ ARM64 Details

Total release size: 54.5 MB

Release files / adbc_driver_hardcharger-2.0.0-py3-none-win_amd64.whl

Download URL adbc_driver_hardcharger-2.0.0-py3-none-win_amd64.whl
Size 11.1 MB
Tags Python 3 Windows x86-64
SHA-256 checksum
How to use checksums
3c7566f4924ff11d02d926311dbb82ff8fcf45a1870ea14ead1727be45f96bba
BLAKE2b-256 checksum
How to use checksums
a35a3efbfa20afc8d882ea90fdb1c629b81da21fd5c8ae783b945b9af1f881e4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.

Transparency log

Release files / adbc_driver_hardcharger-2.0.0-py3-none-manylinux2014_aarch64.manylinux_2_17_aarch64.whl

Download URL adbc_driver_hardcharger-2.0.0-py3-none-manylinux2014_aarch64.manylinux_2_17_aarch64.whl
Size 10.7 MB
Tags Linux glibc 2.17+ ARM64 Python 3
SHA-256 checksum
How to use checksums
a868fa6edfb7debc8a05c0dc1d0063ec822e10423ac8621730e9f038c988d5d5
BLAKE2b-256 checksum
How to use checksums
0cd8ec1392a0d6c72e033ea4260dcaa1e17f331e7ed74f647df67d65cecb5e74
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.

Transparency log

Release files / adbc_driver_hardcharger-2.0.0-py3-none-manylinux1_x86_64.manylinux_2_5_x86_64.whl

Download URL adbc_driver_hardcharger-2.0.0-py3-none-manylinux1_x86_64.manylinux_2_5_x86_64.whl
Size 12.0 MB
Tags Linux glibc 2.5+ x86-64 Python 3
SHA-256 checksum
How to use checksums
f98efa77eee045c592a30397389f07c9ddd057c572c685a1308abb0854f03c44
BLAKE2b-256 checksum
How to use checksums
fda8d589e0a7af170841cfc3b52a5fdf61f7d623f8fd017353a9863d489ad551
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.

Transparency log

Release files / adbc_driver_hardcharger-2.0.0-py3-none-macosx_11_0_x86_64.whl

Download URL adbc_driver_hardcharger-2.0.0-py3-none-macosx_11_0_x86_64.whl
Size 11.0 MB
Tags Python 3 macOS 11.0+ x86-64
SHA-256 checksum
How to use checksums
390f803c161e0c1b62147d08169ccce0cf5cede41f99a19d2950f2afc43aff1d
BLAKE2b-256 checksum
How to use checksums
1f9cf280a52f044db7098958d4c312751dc4b226e06da4e4c490e9fd175ba682
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.

Transparency log

Release files / adbc_driver_hardcharger-2.0.0-py3-none-macosx_11_0_arm64.whl

Download URL adbc_driver_hardcharger-2.0.0-py3-none-macosx_11_0_arm64.whl
Size 9.7 MB
Tags Python 3 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
8bac1962a341b44f23c703a3f655be3fe23f368ac0f4797a25445aeeeea09bc4
BLAKE2b-256 checksum
How to use checksums
f848334840b4d970c9c96f7009f445f458f3313103bc22b7f59e9e00d00fff0b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.

Transparency log

Security for adbc-driver-hardcharger 2.0.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.

Full provenance

All 5 files in this release have been uploaded with provenance metadata.

Select from 5 files

Attestation for adbc_driver_hardcharger-2.0.0-py3-none-win_amd64.whl

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.

Transparency log

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.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

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