What happens?

Passing a config dictionary to duckdb.connect with the documented enable_logging option crashes the Python process with exit code 139 (likely a segfault). An exception cannot be caught.

Tested with Python 3.11.11 and duckdb library versions 1.3.0, 1.2.2, 1.2.1.

To Reproduce

Create a duckdb connection:

python -c 'import duckdb; print(duckdb.connect(config={"enable_logging": 0}))'; echo $?

Observe Python's error exit code:

139

The same operation succeeds with a different duckdb config option:

python -c 'import duckdb; print(duckdb.connect(config={"threads": 1}))'; echo $?

Observe the connection object and Python's successful exit code:

<duckdb.duckdb.DuckDBPyConnection object at 0x10227b670>
0

OS:

MacOS 15.4.1 (24E263) arm64

DuckDB Version:

1.2.1, 1.2.2, 1.3.0

DuckDB Client:

Python

Hardware:

No response

Full Name:

Shahin Saneinejad

Affiliation:

Axiom Bio

What is the latest build you tested with? If possible, we recommend testing with the latest nightly build.

I have tested with a stable release

Did you include all relevant data sets for reproducing the issue?

Yes

Did you include all code required to reproduce the issue?

• Yes, I have

Did you include all relevant configuration (e.g., CPU architecture, Python version, Linux distribution) to reproduce the issue?

• Yes, I have