BSD Ports

databases/py-duckdb 1.5.5 NetBSD

Python module for DuckDB in-process database

System
NetBSD
Repository
pkgsrc
Maintainer
[email protected]
Last update
Commit
65c9b1c391
License
mit
Categories
databases
Package size
13967.0 KiB, 59858.0 KiB installed

Description

DuckDB is a high-performance analytical database system. It is designed to be fast, reliable and easy to use. DuckDB provides a rich SQL dialect, with support far beyond basic SQL. DuckDB supports arbitrary and nested correlated subqueries, window functions, collations, complex types (arrays, structs), and more.

This package provides Python module.

In the other systems

SystemPortVersion
NetBSDdatabases/py-duckdb1.5.5
FreeBSDdatabases/py-duckdb1.5.6

Install

Binary package:

pkgin install py312-duckdb

From pkgsrc:

cd /usr/pkgsrc/databases/py-duckdb && make install clean

Dependencies

Run dependencies 4

No port depends on this one.

Configuration

No options to configure.

Service scripts
none
Flavors
py313-duckdb-1.5.5, py314-duckdb-1.5.5

Commit history 5

DateCommitCreditsLog message
65c9b1c391 adam Forget Python 3.10
1c069cc4e6 ryoon databases/{,py-}duckdb: Update to 1.5.6
Changelog: 1.5.6: What's Changed Use relative includes in unity build sources for cache reuse by @NiclasHaderer in #23972 bump vortex by @samansmink in #24089 [variegata] Remove Julia client in favor of duckdb/DuckDB.jl by @evertlammerts in #24127 [variegata] Replace the C API spec and code generation by @evertlammerts in #24131 TopNWindowElimination Fixes by @d-justen in #24080 Fix active query race by @NiclasHaderer in #24123 Fix UNNEST Pushdown by @d-justen in #24119 [Parquet][Variant] Don't produce VARIANT metadata with sorted_strings set by @Tishj in #23591 Fix LIMIT pushdown through a volatile projection with an OFFSET by @DinosL in #24240 Don't push filters on volatile groups through aggregates by @DinosL in #24239 …
37b4a4c98e jperkin py-duckdb: Pass CMAKE_BUILD_PARALLEL_LEVEL.
Any package that uses py-scikit-build-core to build does not honour MAKE_JOBS. Some packages use make and so are single threaded, but some like duckdb use ninja, and that defaults to ncores+2(!) per build. On my 72-core build host, building 3 py-duckdb packages simultaneously, this is enough to completely swamp things and cause knock-on failures that effectively kill the bulk build. Ideally this needs to be done in a build.mk or similar for py-scikit-build-core but this gets us past this for now.
01661f5d8d ryoon databases/py-duckdb: Update to 1.5.5
Changelog: 1.5.5: What's Changed in DuckDB-Python Fix numpy deprecations by @evertlammerts in #505 Fix alias of DuckDBPyRelation.query (closes #468) by @evertlammerts in #524
ea81ee17e5 ryoon databases/py-duckdb: Update to 1.5.4
Changelog: 1.5.4: What's Changed in DuckDB-Python Make rel->query work with a read only connection by @evertlammerts in #471 Ignore Polars dynamic predicates by @evertlammerts in #482 Accept pathlib.Path, os.PathLike, bytes, and file-like objects in read_parquet/from_parquet by @evertlammerts in #489 Unify arrow exports across all query result types by @evertlammerts in #495