Skip to main content

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.

import bareduckdb

bareduckdb.register_as_duckdb()
import duckdb

print(duckdb.__version__)  # bareduckdb's version
with duckdb.connect() as conn:
    print(conn.execute("PRAGMA version").arrow_table())
    print(conn.execute("select * from range(10)").df())

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.

  • execute() does not run a SELECT. The first fetchall(), df(), pl() or similar runs it. A SELECT you never read never runs.
  • A SELECT is checked when you read it, not at execute(). An error such as an unknown column appears at the first read. A wrong number of parameters still fails at execute().
  • Reading description before any other read runs a SELECT as rows. A later pl() or arrow_table() then builds the table from those rows.
  • A result can be read once, by one method. Calling pl() and then fetchall() raises, and the error names the first method. arrow_table() and df() are the exceptions: you can still fetch rows after them.
  • After an Arrow read, description derives the types from the Arrow schema. Eight types get a different name: HUGEINT, UHUGEINT, TIMETZ, UUID, BIT, JSON, ENUM and TUPLE. With SET arrow_lossless_conversion = true, only ENUM and TUPLE differ.
  • Parameters are typed from the Python value. An int that fits in 32 bits is BIGINT, not INTEGER. An int of 2^63 or more is HUGEINT, not UBIGINT. A dict is a MAP, not a STRUCT, so it cannot be inserted into a STRUCT column. A nested list that mixes types, such as [[1], ['a']], raises.
  • A registered name can appear once per query. A self-join, or a UNION ALL of the name with itself, raises. See "Use a registration twice in one query".
  • Registered names do not appear in SHOW TABLES. A real table with the same name wins.
  • A SELECT whose CTE writes data keeps the write only if you read every row.
  • df() returns pandas ArrowDtype columns, not NumPy columns. Use df(arrow_dtyped=False) for NumPy.
  • VARINT values are int, not str.
  • TIMESTAMPTZ values have a different tzinfo. They compare equal.
  • fetchall() cannot read UNION, VARIANT or GEOMETRY columns. Read them as Arrow. See "DuckDB C API 2.0 limitations".
  • PRAGMA, CALL and RETURNING statements run at execute(). Reading them as Arrow (df(), pl(), arrow_table()) builds the table from the fetched rows, which needs pyarrow and is slower. Some values cannot be rebuilt exactly, such as INTERVAL, BIT, nanosecond timestamps, infinite dates and the time 24:00:00. Those raise, and fetchall() still works. To get Arrow for them, pass output_type="arrow_table" to execute().

Not implemented

  • 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.
  • Some Arrow tables built from rows (see the PRAGMA bullet above). An ENUM column's dictionary holds only the values present. TIMETZ with arrow_lossless_conversion and a MAP with a nested key raise. Memory use is about 2.7 times DuckDB's.

DuckDB C API 2.0 limitations

  • The v2 C API is unstable in DuckDB 2.0.0.
  • Rows cannot be converted to Arrow. PRAGMA, CALL and RETURNING must go through Python -> Arrow. (#25801 removed the old one).
  • An Arrow result has no DuckDB types. description after an Arrow read is derived from the Arrow schema. See "Differences from duckdb-python".
  • VARIANT, UNION and GEOMETRY values cannot be read as rows. fetchall() raises on them. See #27570.
  • A PRAGMA or CALL that returns VARIANT raises on every read, including PRAGMA storage_info. Use the workarounds below.
  • Some VARIANT contents cannot be exported to Arrow: INTERVAL, TIMETZ, BIT, TIMESTAMP_S, TIMESTAMP_MS, and integers larger than int64.
  • v2 C API does not have support appending Use register() with INSERT ... SELECT, or INSERT with parameters.

Workarounds:

conn.execute("select * from pragma_storage_info('t')").arrow_table()  # PRAGMA as a SELECT
conn.execute("select * from duckdb_settings()").df()                  # CALL as a SELECT
conn.execute("pragma storage_info('t')", output_type="arrow_table")   # Arrow from the start

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.200

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.200
File Size Uploaded Provenance Actions
bareduckdb-0.20.200.tar.gz 470.0 kB With provenance Details for bareduckdb-0.20.200.tar.gz

Built distributions (wheels)

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

Total release size: 8.8 MB

Release files / bareduckdb-0.20.200.tar.gz

Download URL bareduckdb-0.20.200.tar.gz
Size 470.0 kB
Tags Source
SHA-256 checksum
How to use checksums
2868a92e3c877b948ee741182dc74456fbadaa18bfc36e527a3f8a8d624d502f
BLAKE2b-256 checksum
How to use checksums
0bf6f1c63b9fb8474f17a6c40d8aaeb258f48e3ab5945ef39f0adc9e006f459e
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 Nov 7, 2026.

Transparency log

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

Download URL bareduckdb-0.20.200-graalpy313-graalpy253_313_native-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 412.9 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
a863192bfc5fb1e8db575e9cc9f1b92274ccf21852bff6dea49de616d69ec008
BLAKE2b-256 checksum
How to use checksums
9682bc08ec7ff63b0373ee8df961c2aba4a63a1284a575f630eca79b23fa7680
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 Nov 7, 2026.

Transparency log

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

Download URL bareduckdb-0.20.200-cp315-cp315t-win_amd64.whl
Size 443.5 kB
Tags CPython 3.15 CPython 3.15 free-threading Windows x86-64
SHA-256 checksum
How to use checksums
9f4117cdf49551ddb263a1df4c4909399849cb0fac68cd5bbf29890c12d459b8
BLAKE2b-256 checksum
How to use checksums
3e107af0aebb64ac70fc3979b463b7169168313448a9b5bfc5251f9c72449cb9
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 Nov 7, 2026.

Transparency log

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

Download URL bareduckdb-0.20.200-cp315-cp315t-musllinux_1_2_x86_64.whl
Size 465.0 kB
Tags CPython 3.15 CPython 3.15 free-threading Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
60eb2f45a7e09e94e2d9378b1dce8348bf1d18c575674b845118db49d1059bbb
BLAKE2b-256 checksum
How to use checksums
66ebb2bbdc97de7652233ae1e4d3ff4028dd0ff93935577fbea0020cec2119f3
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 Nov 7, 2026.

Transparency log

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

Download URL bareduckdb-0.20.200-cp315-cp315t-musllinux_1_2_aarch64.whl
Size 451.7 kB
Tags CPython 3.15 CPython 3.15 free-threading Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
904259d499ebf83664bba0c8862406b662dc00685a2d187eb9f63a01378e6ec3
BLAKE2b-256 checksum
How to use checksums
5b35b36238fe638cc795283f4209f8959f23f51b6aec271fc73f3caba902a847
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 Nov 7, 2026.

Transparency log

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

Download URL bareduckdb-0.20.200-cp315-cp315t-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 462.5 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
0d5123c55323be5d148bcfbb54a1c79e1d10903601fb5b5929b026d2470d87a2
BLAKE2b-256 checksum
How to use checksums
221834e6e473bcffc67dc4466d2b0341d208040dec17c20f7ea12d260b13ca8a
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 Nov 7, 2026.

Transparency log

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

Download URL bareduckdb-0.20.200-cp315-cp315t-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 449.7 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
65ca83ae155f3f9e064eeb55c8925509195fb70dfc7d065d868fc48afbf6af82
BLAKE2b-256 checksum
How to use checksums
665af0aa1dd2186d024ac354bbc8390f037ac5276ea1f46358159e4322ddf7fe
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 Nov 7, 2026.

Transparency log

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

Download URL bareduckdb-0.20.200-cp315-cp315t-macosx_11_0_arm64.whl
Size 418.4 kB
Tags CPython 3.15 CPython 3.15 free-threading macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
041383bcfc02dbc9e42e442083a14b156bbe62e895427ee5c118c1116f6d2c61
BLAKE2b-256 checksum
How to use checksums
1ef2ae2ecf2fd9190b06d09210cb0a91a4036425dc7be4040c6af301f334c7a0
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 Nov 7, 2026.

Transparency log

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

Download URL bareduckdb-0.20.200-cp314-cp314t-win_amd64.whl
Size 446.0 kB
Tags CPython 3.14 CPython 3.14 free-threading Windows x86-64
SHA-256 checksum
How to use checksums
57d92d73cf883223ef1d3f83a0138bfc4280200a59e18242e66feb73ec787b3d
BLAKE2b-256 checksum
How to use checksums
bf14d6dc8ca15fdb5e0abfd95308981d70c55d5af91340b2e524c299f8bc1e64
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 Nov 7, 2026.

Transparency log

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

Download URL bareduckdb-0.20.200-cp314-cp314t-musllinux_1_2_x86_64.whl
Size 465.1 kB
Tags CPython 3.14 CPython 3.14 free-threading Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
f97cc917d46acef7c067fa154bcc60bc641d51a567ee62b4c13312cb007acd17
BLAKE2b-256 checksum
How to use checksums
fdcb97c54e0993137eacbbd048bedc10a71914516f2104cfe13c8594cd2d732d
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 Nov 7, 2026.

Transparency log

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

Download URL bareduckdb-0.20.200-cp314-cp314t-musllinux_1_2_aarch64.whl
Size 453.5 kB
Tags CPython 3.14 CPython 3.14 free-threading Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
04f70e3689d844c2b98fc43e6a63e8118ab136d767fa43ca9aa0bbc956a6eaa6
BLAKE2b-256 checksum
How to use checksums
fc95309e43fe795c723c90ddd9aa3f21d51674c00c96683d8821c5f4e9d50e0d
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 Nov 7, 2026.

Transparency log

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

Download URL bareduckdb-0.20.200-cp314-cp314t-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 462.7 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
5def3f2c0f41021bc276717a22bb64b8f79d026a1ab81fc95178388449d9df07
BLAKE2b-256 checksum
How to use checksums
5eeadf0353b1b60628d89dbd3449cce0ee8893382f3200e4331328e4f392c391
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 Nov 7, 2026.

Transparency log

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

Download URL bareduckdb-0.20.200-cp314-cp314t-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 450.7 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
2dfbf75548cf85228d531d176470f05d471178b487a048f86cd3b4db39aef0e9
BLAKE2b-256 checksum
How to use checksums
34b53083d6445e713618ba76f71a2f4403ea83d5177fe19c8fe02f87747baac0
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 Nov 7, 2026.

Transparency log

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

Download URL bareduckdb-0.20.200-cp314-cp314t-macosx_11_0_arm64.whl
Size 420.3 kB
Tags CPython 3.14 CPython 3.14 free-threading macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
694d7bb27d1da84b036a11010f86c7183d19c1b0978aab8686de9088b5eb652e
BLAKE2b-256 checksum
How to use checksums
086d7c3007b39c2cf4d5ac9309cb51c6736cf39a3a1e7e5176a8f6fc1ca1ab1a
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 Nov 7, 2026.

Transparency log

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

Download URL bareduckdb-0.20.200-cp312-abi3-win_amd64.whl
Size 433.4 kB
Tags CPython 3.12 Windows x86-64 abi3
SHA-256 checksum
How to use checksums
5331ca849402c99dd406b4e51d1594581816a49f3a7e65ff8eb740e71ff177b5
BLAKE2b-256 checksum
How to use checksums
79b3306049b97a99a97063c92076072c2d480a72ae329c5ca0d343d3bb80a4a3
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 Nov 7, 2026.

Transparency log

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

Download URL bareduckdb-0.20.200-cp312-abi3-musllinux_1_2_x86_64.whl
Size 443.2 kB
Tags CPython 3.12 Linux musl 1.2+ x86-64 abi3
SHA-256 checksum
How to use checksums
e7ef07350e507ee4c3bb921428cbd349bc22d4937852271c8ed58d9b9a6961c9
BLAKE2b-256 checksum
How to use checksums
842c3fa166a38ade7304d881c7ea98516abdef3370217a9613340c7cb1fcebaa
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 Nov 7, 2026.

Transparency log

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

Download URL bareduckdb-0.20.200-cp312-abi3-musllinux_1_2_aarch64.whl
Size 424.4 kB
Tags CPython 3.12 Linux musl 1.2+ ARM64 abi3
SHA-256 checksum
How to use checksums
a896fdb1997d1eccccfdf54ffad21313ab60f36259aa5d558f624934650e21dc
BLAKE2b-256 checksum
How to use checksums
16f089159c524f7442d27ddbd84e2e46bdef5ff5606a62d707e8ce72e5ae1a00
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 Nov 7, 2026.

Transparency log

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

Download URL bareduckdb-0.20.200-cp312-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 441.3 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
f9e0e2edeb3d66f7566e7d3fc8bd588c1c3efa60321441158358b3c5ce251473
BLAKE2b-256 checksum
How to use checksums
74f6ad26ce08d55a2841e78ad00cb55590a5d097b8d327cb6dcd941bc4777924
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 Nov 7, 2026.

Transparency log

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

Download URL bareduckdb-0.20.200-cp312-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 424.6 kB
Tags CPython 3.12 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64 abi3
SHA-256 checksum
How to use checksums
97abff9c9400e9a4ea09651a325a73e3ea38bf9353bfa7397ec7083d06ad133c
BLAKE2b-256 checksum
How to use checksums
a4c4a9628a080de3212d8357f6143188dfaaed2f20483f2905cf87a6c754a705
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 Nov 7, 2026.

Transparency log

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

Download URL bareduckdb-0.20.200-cp312-abi3-macosx_11_0_arm64.whl
Size 398.1 kB
Tags CPython 3.12 abi3 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
334a2df916e44d418962627024fe80527bff862cd3db5023f57f828ddcad79b3
BLAKE2b-256 checksum
How to use checksums
877f1f141cdc41fad4c131ede9fa78dac6a9369ad55d8e9246f37c15356cbccc
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 Nov 7, 2026.

Transparency log

Security for bareduckdb 0.20.200

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.200.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 Nov 7, 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