Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

bareduckdb

Python bindings for DuckDB 2.0, bound only to DuckDB's v2 C API (duckdb_v2_*). bareduckdb does not vendor or build DuckDB. It loads the official libduckdb shared library from DuckDB's release, so the engine is upstream's release build.

PyPI version Python 3.12+ License: MIT

pip install bareduckdb

The first import downloads libduckdb; see "The DuckDB library".

import bareduckdb
import polars as pl

with bareduckdb.connect() as conn:
    conn.register("t", pl.DataFrame({"a": [1, 2, 3]}))
    conn.execute("SELECT sum(a) AS s FROM t").pl()         # polars frame, s = 6, no pyarrow
    conn.execute("SELECT 42 AS answer").fetchall()         # [(42,)]

Design

Querying Python data

  • Registration is explicit. Pass a DataFrame, Arrow table or pl.LazyFrame inline with conn.execute(sql, data={"t": df}), or register it on the connection with conn.register("t", df). A query sees only objects named one of these ways. duckdb-python can also find variables in the caller's scope; bareduckdb leaves that out.
  • Input is zero-copy for Arrow and polars data. It is read in place and on demand, so a LIMIT reads only the batches it needs and a pl.LazyFrame is streamed, never collected.
  • polars goes in through its own Arrow C stream and comes out through .pl() the same way, without importing pyarrow. CI runs a leg with pyarrow uninstalled.

Free threading

Wheels ship for free-threaded 3.14t and 3.15t. Every engine call runs with the GIL released, and every extension module declares itself free-threading compatible.

Packaging

Wheels are under 400 KB and have no required Python dependencies; pyarrow, polars and pandas are optional and imported on demand. The DuckDB library, 20 to 40 MB compressed, is downloaded from DuckDB's release server on first import and cached.

Guides

Run a query

import bareduckdb

with bareduckdb.connect() as conn:                     # or connect("file.db")
    conn.execute("CREATE TABLE t AS SELECT * FROM range(100) AS r(a)")
    conn.execute("SELECT * FROM t WHERE a > ?", [10]).fetchall()       # positional
    conn.execute("SELECT * FROM t WHERE a > $x", {"x": 10}).fetchall()  # named

    conn.execute("SELECT * FROM t").pl()            # polars
    conn.execute("SELECT * FROM t").arrow_table()   # pyarrow
    conn.execute("SELECT * FROM t").df()            # pandas, ArrowDtype columns

Query in-memory data

register() names an object on the connection until unregister() or the connection closes.

import bareduckdb
import polars as pl
import pyarrow as pa

orders = pl.DataFrame({"id": [1, 2, 3], "amount": [10.0, 25.0, 5.0]})

with bareduckdb.connect() as conn:
    conn.register("orders", orders)
    conn.execute("SELECT sum(amount) AS total FROM orders").pl()

    conn.register("events", pl.scan_parquet("events/*.parquet"))   # streamed, not collected
    conn.execute("SELECT count(*) FROM events WHERE kind = 'click'").pl()

    conn.unregister("orders")

execute(..., data=...) names objects for that one call, and the names are gone when the call returns.

customers = pa.table({"id": [1, 2, 3], "name": ["a", "b", "c"]})

with bareduckdb.connect() as conn:
    conn.execute(
        "SELECT c.name, o.amount FROM o JOIN c USING (id) WHERE o.amount > ?",
        [8],
        data={"o": orders, "c": customers},
    ).fetchall()
    # [('a', 10.0), ('b', 25.0)]

A variable named neither way is not found, even if it is in scope: SELECT * FROM customers above raises a catalog error. "Registered sources" below lists what both accept and how each source type is read.

Use a registration twice in one query

A registration can be scanned once per query, so a self-join or a UNION ALL over the same name raises. Read it through a materialized CTE instead:

WITH c AS MATERIALIZED (SELECT id, amount FROM orders)
SELECT count(*) FROM c x JOIN c y USING (id)

The registration is scanned once, and the CTE holds a copy of the selected columns until the query ends. Write MATERIALIZED explicitly. Without it DuckDB may inline the CTE, which it does when the query has a LIMIT, and the second scan raises. A CTE does not help concurrent queries from other cursors.

Stream a large result in batches

reader = conn.execute("SELECT * FROM range(10_000_000)").arrow_reader(batch_size=100_000)
for batch in reader:
    ...

A reader holds its query open until it is read to the end, it is deleted, or the connection runs its next statement. After that, a reader still referenced raises ArrowInvalid on its next read, where duckdb-python ends it without an error. reader.close() does not release the query. Use conn.cursor() to keep a reader open while running other queries.

Cancel a query and show progress

import threading
from bareduckdb import QueryCancelled, enable_progress, poll_progress

with bareduckdb.connect() as conn:
    threading.Timer(5.0, conn.interrupt).start()
    try:
        conn.execute("SELECT ... FROM big").fetchall()
    except QueryCancelled:
        pass
    conn.execute("SELECT 42").fetchall()            # the connection is still usable

    enable_progress(conn)
    with poll_progress(conn, lambda p: print(f"{p.percentage:.0f}%")):
        conn.execute("SELECT ... FROM big").pl()

interrupt() works from any thread. On a GIL build it cannot stop .pl() mid-read, because polars holds the GIL while it reads. max_execution_time still applies, and arrow_table() and arrow_reader() can be interrupted. See README_PROGRESS.md.

Run queries from asyncio or trio

The async pool is built on anyio. Each query runs on a cursor in a worker thread, and cancelling the awaiting task interrupts the query. Results come back as pyarrow.Table, so the pool needs pyarrow as well as the aio extra.

pip install "bareduckdb[aio,arrow]"
from bareduckdb.aio import AsyncConnectionPool

async with AsyncConnectionPool(":memory:", pool_size=4) as pool:
    table = await pool.execute("SELECT * FROM range(?)", parameters=(10,))

A cancelled execute returns once the interrupt has stopped the worker thread, about 2 ms after the cancel (see README_PROGRESS.md), and the cursor is free by then. anyio's move_on_after and fail_after work on either backend, and asyncio.wait_for works under asyncio.

Use bareduckdb where duckdb is expected

bareduckdb.register_as_duckdb() aliases the duckdb module to bareduckdb. CI runs SQLAlchemy (duckdb-engine), jupysql and magic-duckdb this way.

Run without network access

In a container, mount the cache directory (see "The DuckDB library"), or the download repeats on every run. For an air-gapped host, fetch the library elsewhere and point bareduckdb at it:

python -m bareduckdb.install_duckdb --dir /opt/duckdb    # on a machine with network access
export BAREDUCKDB_DUCKDB_LIB=/opt/duckdb                 # on the target
export BAREDUCKDB_NO_DOWNLOAD=1                          # fail instead of downloading

With BAREDUCKDB_NO_DOWNLOAD set and nothing found, import raises DuckDBLibraryNotFoundError, listing every path it tried.

Reference

Connection

bareduckdb.connect(database=None, config=None, read_only=False, *, parse_cache_size=128) opens a connection; None is an in-memory database. config takes DuckDB settings, for example {"threads": "4", "memory_limit": "1GB"}. The connection is a context manager that closes on exit.

Method Effect
execute(sql, parameters=None, *, data=None) Runs a statement and returns the connection, whose result methods read that statement's result. data names objects for this call only.
register(name, obj) Names an object until unregister() or close. Returns the connection.
unregister(name) Removes a name. An unknown name is a no-op. Returns the connection.
cursor() A new connection to the same database, with its own result state.
interrupt() Cancels the running query from any thread; it raises QueryCancelled.
close() Closes the connection.

Each connection keeps the last parse_cache_size parsed single-statement SELECTs, keyed by SQL text, so a repeated query skips the parse. Bind and execute still run every time, and any other statement clears the cache. 0 turns it off.

Results

These are called on the connection after execute(), as in conn.execute(sql).pl().

Method Returns Needs
fetchone(), fetchmany(n), fetchall() tuples nothing
pl() pl.DataFrame polars
pl_lazy() pl.LazyFrame over the stream polars and pyarrow
arrow_table() pa.Table pyarrow
arrow_reader(batch_size=None) pa.RecordBatchReader pyarrow
df(arrow_dtyped=True) pd.DataFrame pandas and pyarrow
description, columns, rowcount metadata nothing

A result is consumed once. rowcount is the changed-row count for INSERT, UPDATE and DELETE, and -1 otherwise.

Registered sources

register() and data= accept polars DataFrames and LazyFrames, pyarrow Tables, Datasets, Scanners and RecordBatchReaders, pandas DataFrames, and any object with __arrow_c_stream__.

  • Arrow and polars data is read in place. Columns the query does not name are never converted.
  • pandas frames are converted with pyarrow.Table.from_pandas, which needs pyarrow and copies numpy-backed columns.
  • A pa.RecordBatchReader is read fully at registration.
  • A registration is re-read on every query, so a pl.LazyFrame re-runs its pipeline each time. For a frame that fits in memory and is queried repeatedly, .collect() it first.
  • Filters are not pushed into the source. A pl.LazyFrame is asked for every row and DuckDB applies the WHERE.
  • The planner gets a row count only for a source with a len(): a pa.Table, pl.DataFrame or pandas frame. Without one, DuckDB can pick a full sort over a top-N for a large ORDER BY ... LIMIT.
  • Insertion order is preserved by default, as in DuckDB, and scans stay parallel. SET preserve_insertion_order=false opts into the unordered, lower-memory sink.

Environment variables

Variable When Effect
BAREDUCKDB_DUCKDB_LIB import Path to libduckdb, or to a directory holding it. Checked first.
BAREDUCKDB_NO_DOWNLOAD import Raise instead of downloading libduckdb.
BAREDUCKDB_LOG_LEVEL import Configures logging at this level, for example DEBUG.
BAREDUCKDB_COLLECT_LAZYFRAME query 1 collects a pl.LazyFrame instead of streaming it. A measurement toggle, off by default.
BAREDUCKDB_DUCKDB_DIR build Use a local libduckdb directory instead of downloading one.
BAREDUCKDB_DUCKDB_CHANNEL build stable (default) or preview, DuckDB's rolling preview build.
BAREDUCKDB_DUCKDB_VERSION build Stable release tag to fetch. Empty uses the pinned release.
BAREDUCKDB_DUCKDB_ARTIFACT build Override the platform artifact name, for example linux-arm64-musl.

Platforms

Linux glibc (manylinux_2_28) Linux musl (musllinux_1_2) macOS Windows
x86_64 yes yes no yes
arm64 yes yes yes no

One cp312-abi3 limited-API wheel covers GIL builds of CPython 3.12 and newer. cp314t and cp315t wheels cover free-threaded CPython. GraalPy 25.3 (Python 3.13) is built for Linux x86_64 only; see README_GRAALPY.md. PyPy is not supported.

Every CPython wheel runs the core test suite before upload, and the GraalPy wheel runs a subset. For thread safety, the suite also runs under pytest-run-parallel on 3.14 and 3.15t on Linux, macOS and Windows, and TSAN and ASAN builds run nightly on free-threaded 3.14.

The DuckDB library

The wheel does not contain libduckdb. On first import, bareduckdb looks for it in this order:

  1. BAREDUCKDB_DUCKDB_LIB, a path to the library file or to a directory holding it.
  2. bareduckdb/_libs/ inside the package, which only a source build fills.
  3. The user cache: ~/.cache/bareduckdb ($XDG_CACHE_HOME), ~/Library/Caches/bareduckdb, or %LOCALAPPDATA%\bareduckdb\Cache.
  4. A download of the pinned release, currently v2.0.0, from install.duckdb.org/v2.0.0/duckdb-shared-libs-<platform>.tar.gz, into that cache.

The first import therefore needs network access, once per user and DuckDB version. The download is checked for CPU architecture but not against a checksum or signature. It relies on HTTPS.

SELECT * FROM pragma_version() reports DuckDB's own version and source id. Extensions load from DuckDB's extension directory (~/.duckdb/extensions/v2.0.0/...). duckdb and bareduckdb can be imported in the same process.

Differences from duckdb-python

Defaults follow DuckDB, with these differences.

  • A SELECT runs at its first consumer, not at execute(). Bind errors still raise at execute(). A SELECT that is never read never runs.
  • Mixing consumers on one result raises, for example .pl() then .fetchall(). arrow_table() is exempt, and rows can still be fetched after it. Repeating the same call behaves like duckdb-python.
  • A registration can be scanned once per query, so a self-join, a UNION ALL over the same name, or a concurrent query from another cursor raises. See "Use a registration twice in one query".
  • Registrations do not appear in SHOW TABLES, and they do not shadow a real table of the same name.
  • A SELECT with a data-modifying CTE keeps its write only if read to the end.
  • df() returns ArrowDtype columns, not NumPy dtypes. df(arrow_dtyped=False) gives pyarrow's default conversion.
  • VARINT returns int, not str.
  • TIMESTAMPTZ values compare equal to duckdb-python's but carry a different tzinfo.
  • UNION and VARIANT raise from fetchall() and work through Arrow.

Not implemented

  • The appender, executemany, and the module-level functions (bareduckdb.sql, read_csv, ...). These raise NotImplementedError.
  • Python table functions and replacement scans. register_udtf(), a non-empty connect(udtf_functions=...) and connect(enable_replacement_scan=True) raise NotImplementedError. Use register() instead.
  • The relation API. Use SQL, or a frontend such as ibis or narwhals.
  • Python scalar UDFs and fsspec filesystems.
  • Filter pushdown into registered sources.

Why it works this way

A SELECT waits for its first consumer. DuckDB fixes a result's format, rows or Arrow, when the query is submitted, and offers no conversion afterwards. Submitting at execute() would mean guessing the format, and running the query twice whenever the guess was wrong.

A registration is scanned once per query. The scan converts one Arrow batch at a time per worker and discards each converted chunk as soon as it is emitted. Peak memory for a scan stays at about one chunk per thread whatever the source's size, and there is nothing left over for a second scan of the same name to replay. A materialized CTE makes that copy explicitly, for one query.

libduckdb is downloaded, not bundled. Linking DuckDB's own release build keeps the wheels small and the engine identical to upstream's. Moving to a new DuckDB release is a re-pin, not a rebuild of DuckDB.

Some features wait on the C API. The v2 C API has no appender yet, and its parse_sql exposes no table references or function-call sites, so Python table functions and replacement scans cannot be discovered from SQL. Filter pushdown, the appender and table functions existed in bareduckdb 0.12 on the 1.x API and need porting. Scalar UDFs and filesystems need DuckDB threads to call back into Python, which needs design work first.

Selective filters are slower than in duckdb-python. Without filter pushdown, every row of the named columns is converted before DuckDB filters it. Filtering in the source wins below roughly 20% selectivity and loses above it.

Development

uv pip install -e .                       # scikit-build-core + CMake; fetches libduckdb on first build
uv run pytest tests/capi -o addopts= -q   # fast subset
uv run pre-commit run --all-files

A source build compiles five Cython modules and downloads libduckdb at build time, unless BAREDUCKDB_DUCKDB_DIR points at a local copy. Windows needs MSVC. Editing a .pyx or .pxd requires a rebuild. polars and vortex-data are in the dev-gil group, which is not installed by default. On a GIL build, add them with uv pip install --group dev-gil --only-binary :all:.

The binding uses only released, non-deprecated duckdb_v2_* functions. Upstream marks all of them unstable: v2.0.0, so a signature can change between releases. tests/capi/pxd_prototypes.txt pins the header prototype of every function the binding declares, and a re-pin that changes one fails until the snapshot is regenerated.

libduckdb is loaded with RTLD_LOCAL, which keeps its symbols apart from the official duckdb wheel's statically linked copy when both are imported. pyarrow's from_batches reader has a no-op close(), which is why reader.close() does not release a query.

Disclaimer

Not affiliated with DuckDB Labs or the DuckDB Foundation.

License

MIT. See LICENSE.

Metadata

Release files for bareduckdb 0.20.200b2

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

Source distribution (sdist)

Source distribution for bareduckdb 0.20.200b2
File Size Uploaded Provenance Actions
bareduckdb-0.20.200b2.tar.gz 444.5 kB With provenance Details for bareduckdb-0.20.200b2.tar.gz

Built distributions (wheels)

Table of built distributions (wheels) for bareduckdb 0.20.200b2
File Actions
bareduckdb-0.20.200b2-graalpy313-graalpy253_313_native-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl graalpy313 graalpy253 313 native Linux glibc 2.17+ x86-64, Linux glibc 2.28+ x86-64 Details for bareduckdb-0.20.200b2-graalpy313-graalpy253_313_native-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
bareduckdb-0.20.200b2-cp315-cp315t-win_amd64.whl CPython 3.15 CPython 3.15 free-threading Windows x86-64 Details for bareduckdb-0.20.200b2-cp315-cp315t-win_amd64.whl
bareduckdb-0.20.200b2-cp315-cp315t-musllinux_1_2_x86_64.whl CPython 3.15 CPython 3.15 free-threading Linux musl 1.2+ x86-64 Details for bareduckdb-0.20.200b2-cp315-cp315t-musllinux_1_2_x86_64.whl
bareduckdb-0.20.200b2-cp315-cp315t-musllinux_1_2_aarch64.whl CPython 3.15 CPython 3.15 free-threading Linux musl 1.2+ ARM64 Details for bareduckdb-0.20.200b2-cp315-cp315t-musllinux_1_2_aarch64.whl
bareduckdb-0.20.200b2-cp315-cp315t-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.15 CPython 3.15 free-threading Linux glibc 2.17+ x86-64, Linux glibc 2.28+ x86-64 Details for bareduckdb-0.20.200b2-cp315-cp315t-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
bareduckdb-0.20.200b2-cp315-cp315t-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl CPython 3.15 CPython 3.15 free-threading Linux glibc 2.28+ ARM64, Linux glibc 2.17+ ARM64 Details for bareduckdb-0.20.200b2-cp315-cp315t-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
bareduckdb-0.20.200b2-cp315-cp315t-macosx_11_0_arm64.whl CPython 3.15 CPython 3.15 free-threading macOS 11.0+ ARM64 Details for bareduckdb-0.20.200b2-cp315-cp315t-macosx_11_0_arm64.whl
bareduckdb-0.20.200b2-cp314-cp314t-win_amd64.whl CPython 3.14 CPython 3.14 free-threading Windows x86-64 Details for bareduckdb-0.20.200b2-cp314-cp314t-win_amd64.whl
bareduckdb-0.20.200b2-cp314-cp314t-musllinux_1_2_x86_64.whl CPython 3.14 CPython 3.14 free-threading Linux musl 1.2+ x86-64 Details for bareduckdb-0.20.200b2-cp314-cp314t-musllinux_1_2_x86_64.whl
bareduckdb-0.20.200b2-cp314-cp314t-musllinux_1_2_aarch64.whl CPython 3.14 CPython 3.14 free-threading Linux musl 1.2+ ARM64 Details for bareduckdb-0.20.200b2-cp314-cp314t-musllinux_1_2_aarch64.whl
bareduckdb-0.20.200b2-cp314-cp314t-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.14 CPython 3.14 free-threading Linux glibc 2.28+ x86-64, Linux glibc 2.17+ x86-64 Details for bareduckdb-0.20.200b2-cp314-cp314t-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
bareduckdb-0.20.200b2-cp314-cp314t-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl CPython 3.14 CPython 3.14 free-threading Linux glibc 2.28+ ARM64, Linux glibc 2.17+ ARM64 Details for bareduckdb-0.20.200b2-cp314-cp314t-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
bareduckdb-0.20.200b2-cp314-cp314t-macosx_11_0_arm64.whl CPython 3.14 CPython 3.14 free-threading macOS 11.0+ ARM64 Details for bareduckdb-0.20.200b2-cp314-cp314t-macosx_11_0_arm64.whl
bareduckdb-0.20.200b2-cp312-abi3-win_amd64.whl CPython 3.12 abi3 Windows x86-64 Details for bareduckdb-0.20.200b2-cp312-abi3-win_amd64.whl
bareduckdb-0.20.200b2-cp312-abi3-musllinux_1_2_x86_64.whl CPython 3.12 abi3 Linux musl 1.2+ x86-64 Details for bareduckdb-0.20.200b2-cp312-abi3-musllinux_1_2_x86_64.whl
bareduckdb-0.20.200b2-cp312-abi3-musllinux_1_2_aarch64.whl CPython 3.12 abi3 Linux musl 1.2+ ARM64 Details for bareduckdb-0.20.200b2-cp312-abi3-musllinux_1_2_aarch64.whl
bareduckdb-0.20.200b2-cp312-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.12 abi3 Linux glibc 2.17+ x86-64, Linux glibc 2.28+ x86-64 Details for bareduckdb-0.20.200b2-cp312-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
bareduckdb-0.20.200b2-cp312-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl CPython 3.12 abi3 Linux glibc 2.28+ ARM64, Linux glibc 2.17+ ARM64 Details for bareduckdb-0.20.200b2-cp312-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
bareduckdb-0.20.200b2-cp312-abi3-macosx_11_0_arm64.whl CPython 3.12 abi3 macOS 11.0+ ARM64 Details for bareduckdb-0.20.200b2-cp312-abi3-macosx_11_0_arm64.whl

Total release size: 8.6 MB

Release files / bareduckdb-0.20.200b2.tar.gz

Download URL bareduckdb-0.20.200b2.tar.gz
Size 444.5 kB
Tags Source
SHA-256 checksum
How to use checksums
e9443dde9e87302c117c7e76d1e489e178e2a9f5c77dae2ce48db1d3e3726a98
BLAKE2b-256 checksum
How to use checksums
0b9bf62f675b8915c804c01d6041551aded0b99dc4fbb49b449dc8813c5f4c64
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 24, 2026.

Transparency log

Release files / bareduckdb-0.20.200b2-graalpy313-graalpy253_313_native-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL bareduckdb-0.20.200b2-graalpy313-graalpy253_313_native-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 399.5 kB
Tags Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64 graalpy253 313 native graalpy313
SHA-256 checksum
How to use checksums
5fa69735339b1bcde19f7e8ff354df6e82973880d56dcefaea43b8491a98fea5
BLAKE2b-256 checksum
How to use checksums
d159edd3aa9d7eecbfe756aed1efd17a068d4454faec687f1120d124d6fcebb8
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 24, 2026.

Transparency log

Release files / bareduckdb-0.20.200b2-cp315-cp315t-win_amd64.whl

Download URL bareduckdb-0.20.200b2-cp315-cp315t-win_amd64.whl
Size 431.2 kB
Tags CPython 3.15 CPython 3.15 free-threading Windows x86-64
SHA-256 checksum
How to use checksums
fb23ec00c0df31ebc8b8ebe3ef910d0adf8456d01f24aa394943460e92914eb7
BLAKE2b-256 checksum
How to use checksums
7dd007e79b9e678b04650ac20a1cbf7a611f907ada7fd74f8c67e5bbf9d8c9df
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 24, 2026.

Transparency log

Release files / bareduckdb-0.20.200b2-cp315-cp315t-musllinux_1_2_x86_64.whl

Download URL bareduckdb-0.20.200b2-cp315-cp315t-musllinux_1_2_x86_64.whl
Size 451.2 kB
Tags CPython 3.15 CPython 3.15 free-threading Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
5626cc500bb646173df50c289cdbc41b1a45039af4d6633da9fbe6823711c44c
BLAKE2b-256 checksum
How to use checksums
68edf9a716b919797d589b4b5af4e09f04f5df9d61b9aaaf417c63a9a9b259b7
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 24, 2026.

Transparency log

Release files / bareduckdb-0.20.200b2-cp315-cp315t-musllinux_1_2_aarch64.whl

Download URL bareduckdb-0.20.200b2-cp315-cp315t-musllinux_1_2_aarch64.whl
Size 438.8 kB
Tags CPython 3.15 CPython 3.15 free-threading Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
38ae6c2f69d4671694d2286c2c1b0ce8b7d21e6de71a3aea0bf9f9fa320fb6de
BLAKE2b-256 checksum
How to use checksums
a74fe2399773db2f299417d8c6e028bca605c40b28446c49c702bbf476f1c7d7
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 24, 2026.

Transparency log

Release files / bareduckdb-0.20.200b2-cp315-cp315t-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL bareduckdb-0.20.200b2-cp315-cp315t-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 448.8 kB
Tags CPython 3.15 CPython 3.15 free-threading Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
5ccddd2733efeec60f24ec86f170d39a58fb0ea932bbb6c7fdadd6e0c7ba4cf8
BLAKE2b-256 checksum
How to use checksums
73248f4fbd833ac8cb73cd0aaab661306e71502a7d52446f91becee95040853c
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 24, 2026.

Transparency log

Release files / bareduckdb-0.20.200b2-cp315-cp315t-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl

Download URL bareduckdb-0.20.200b2-cp315-cp315t-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 437.0 kB
Tags CPython 3.15 CPython 3.15 free-threading Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
e2ab1cc6f3ac3f2b825e579230df121748b952d3b815e73b9d4279e5600bd0ea
BLAKE2b-256 checksum
How to use checksums
08cf7380d93577aba4d5d732df0836b48fa30dd28ffd399a83e008ccc69a41a2
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 24, 2026.

Transparency log

Release files / bareduckdb-0.20.200b2-cp315-cp315t-macosx_11_0_arm64.whl

Download URL bareduckdb-0.20.200b2-cp315-cp315t-macosx_11_0_arm64.whl
Size 406.1 kB
Tags CPython 3.15 CPython 3.15 free-threading macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
61661a39ef568fae5eec3a868d1098cd8d1392c76531b3d0abac125306e762bf
BLAKE2b-256 checksum
How to use checksums
d0431c18cab247123936f1a5ffc050fa3a244941a33b66db26b6b0fcf4ccde33
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 24, 2026.

Transparency log

Release files / bareduckdb-0.20.200b2-cp314-cp314t-win_amd64.whl

Download URL bareduckdb-0.20.200b2-cp314-cp314t-win_amd64.whl
Size 433.6 kB
Tags CPython 3.14 CPython 3.14 free-threading Windows x86-64
SHA-256 checksum
How to use checksums
0cf7db3bfd2cfe55f4483da40ca0ee641f5c7c29ac6bfb0c219fe91799c5169a
BLAKE2b-256 checksum
How to use checksums
9c748106bd88a301ca9fa23e59c1e1906bf04d14efb8028abf48504463efa5fc
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 24, 2026.

Transparency log

Release files / bareduckdb-0.20.200b2-cp314-cp314t-musllinux_1_2_x86_64.whl

Download URL bareduckdb-0.20.200b2-cp314-cp314t-musllinux_1_2_x86_64.whl
Size 451.6 kB
Tags CPython 3.14 CPython 3.14 free-threading Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
20021f286795445dbe5652641fb089542c6017b81c64d5dace79c63935579dc5
BLAKE2b-256 checksum
How to use checksums
8d09b8e74e68cb9cd0627de4f644ed2652100faeb02a8482b8a7d2e828d515fa
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 24, 2026.

Transparency log

Release files / bareduckdb-0.20.200b2-cp314-cp314t-musllinux_1_2_aarch64.whl

Download URL bareduckdb-0.20.200b2-cp314-cp314t-musllinux_1_2_aarch64.whl
Size 440.8 kB
Tags CPython 3.14 CPython 3.14 free-threading Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
89065426921178376540fb1af02c4da72d6fa5b7b1ce19349567869b6f8ff670
BLAKE2b-256 checksum
How to use checksums
bab8a083c17f3a5ec61b2dd87345272e464dccc01525177a529ddec0017da1cf
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 24, 2026.

Transparency log

Release files / bareduckdb-0.20.200b2-cp314-cp314t-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL bareduckdb-0.20.200b2-cp314-cp314t-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 449.5 kB
Tags CPython 3.14 CPython 3.14 free-threading Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
f7b34d675a0309cb8004a7da30a01fb5f3b85641c8268b39e6e05ee2c5e5de90
BLAKE2b-256 checksum
How to use checksums
f79bd0d355abea5c5da54b7cc2678b9035aacd14bbcf145b85b161827e77f45d
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 24, 2026.

Transparency log

Release files / bareduckdb-0.20.200b2-cp314-cp314t-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl

Download URL bareduckdb-0.20.200b2-cp314-cp314t-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 438.2 kB
Tags CPython 3.14 CPython 3.14 free-threading Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
37dc6d46916a7c15f610a33fc0a66489ac824f07c45919edfccc302d88c06fcf
BLAKE2b-256 checksum
How to use checksums
a3aafee83ee2ecf21dfb00d5308c30e4048026a1c05480ece453d1b4bb990bca
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 24, 2026.

Transparency log

Release files / bareduckdb-0.20.200b2-cp314-cp314t-macosx_11_0_arm64.whl

Download URL bareduckdb-0.20.200b2-cp314-cp314t-macosx_11_0_arm64.whl
Size 408.1 kB
Tags CPython 3.14 CPython 3.14 free-threading macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
058643ea241683f92261e6a2308abd03e3973d98eb2c79174367477f253f093d
BLAKE2b-256 checksum
How to use checksums
33150f20a912ece3d31fd9878c8ed39e0dbf09040b2fd9e4ae35e48169c52c3d
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 24, 2026.

Transparency log

Release files / bareduckdb-0.20.200b2-cp312-abi3-win_amd64.whl

Download URL bareduckdb-0.20.200b2-cp312-abi3-win_amd64.whl
Size 421.3 kB
Tags CPython 3.12 Windows x86-64 abi3
SHA-256 checksum
How to use checksums
c3547d6097590a7d7831c2194fb479a638e15a5d34497b7e5cebcfd202170bbc
BLAKE2b-256 checksum
How to use checksums
57c34b25bafb5f14537df2ffe85f1844149f9cb1c8810559be21a293307f6760
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 24, 2026.

Transparency log

Release files / bareduckdb-0.20.200b2-cp312-abi3-musllinux_1_2_x86_64.whl

Download URL bareduckdb-0.20.200b2-cp312-abi3-musllinux_1_2_x86_64.whl
Size 430.7 kB
Tags CPython 3.12 Linux musl 1.2+ x86-64 abi3
SHA-256 checksum
How to use checksums
0cf281b6086d6466c2623b0bbafc95edbf3d0c190ce79543aea792545526762f
BLAKE2b-256 checksum
How to use checksums
142d1e85da167b942ca354a3fb93526e9b76a01922910df7920628b48b641833
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 24, 2026.

Transparency log

Release files / bareduckdb-0.20.200b2-cp312-abi3-musllinux_1_2_aarch64.whl

Download URL bareduckdb-0.20.200b2-cp312-abi3-musllinux_1_2_aarch64.whl
Size 413.2 kB
Tags CPython 3.12 Linux musl 1.2+ ARM64 abi3
SHA-256 checksum
How to use checksums
2e42ee4fc5443b914c093459f1f135463ae7ff155102f50ee9fa50ed7d09ae34
BLAKE2b-256 checksum
How to use checksums
38eab3a0b4ad26dfb2277df54aed2092ca8336a46baff611b83dfde2d90990af
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 24, 2026.

Transparency log

Release files / bareduckdb-0.20.200b2-cp312-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL bareduckdb-0.20.200b2-cp312-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 428.8 kB
Tags CPython 3.12 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64 abi3
SHA-256 checksum
How to use checksums
e22c06ee81a1c93b7f840d060c3dc5c12fdba75b3aaa8f33fb30f0541bd0daf7
BLAKE2b-256 checksum
How to use checksums
393eb3c11454c5e5befeb7baef96b3659e360059ab94c84be9bf9cdb6e17779b
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 24, 2026.

Transparency log

Release files / bareduckdb-0.20.200b2-cp312-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl

Download URL bareduckdb-0.20.200b2-cp312-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 412.9 kB
Tags CPython 3.12 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64 abi3
SHA-256 checksum
How to use checksums
13bd9addcc183e0795c235f7a3b7f5ba68e443d5e685f0941e64377debfc8d09
BLAKE2b-256 checksum
How to use checksums
912c35f801f8b9e72be274de0b25524f57925f4b84ee153e43736007dbf2036c
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 24, 2026.

Transparency log

Release files / bareduckdb-0.20.200b2-cp312-abi3-macosx_11_0_arm64.whl

Download URL bareduckdb-0.20.200b2-cp312-abi3-macosx_11_0_arm64.whl
Size 385.5 kB
Tags CPython 3.12 abi3 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
d17ff68d47c853e103db483b4507a075e38687a1e8cad085354b67ecc0b5cdc6
BLAKE2b-256 checksum
How to use checksums
fb6aab01fe3612dff418067dc77d03f1eb73488e08eea058e9f10a56eb63704f
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 24, 2026.

Transparency log

Security for bareduckdb 0.20.200b2

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 20 files in this release have been uploaded with provenance metadata.

Select from 20 files

Attestation for bareduckdb-0.20.200b2.tar.gz

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 24, 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