What happens?
In duckdb 1.4.1, the type definition of the config dict passed into .connect is Dict[str, str]. However, even the most simple example in the documentation contains an int: https://duckdb.org/docs/stable/clients/python/overview.html#configuration
What's the best practice here now: should str() it all? Is the correct representation for booleans False or false?
To Reproduce
send https://duckdb.org/docs/stable/clients/python/overview.html#configuration through mypy.
OS:
OSX
DuckDB Package Version:
1.4.1
Python Version:
3.12
Full Name:
Friedrich Lindenberg
Affiliation:
OpenSanctions
What is the latest build you tested with? If possible, we recommend testing with the latest nightly build.
I have not tested with any build
Did you include all relevant data sets for reproducing the issue?
Not applicable - the reproduction does not require a data set
Did you include all code required to reproduce the issue?
Did you include all relevant configuration to reproduce the issue?
What happens?
In duckdb 1.4.1, the type definition of the config dict passed into .connect is
Dict[str, str]. However, even the most simple example in the documentation contains anint: https://duckdb.org/docs/stable/clients/python/overview.html#configurationWhat's the best practice here now: should str() it all? Is the correct representation for booleans
Falseorfalse?To Reproduce
send https://duckdb.org/docs/stable/clients/python/overview.html#configuration through mypy.
OS:
OSX
DuckDB Package Version:
1.4.1
Python Version:
3.12
Full Name:
Friedrich Lindenberg
Affiliation:
OpenSanctions
What is the latest build you tested with? If possible, we recommend testing with the latest nightly build.
I have not tested with any build
Did you include all relevant data sets for reproducing the issue?
Not applicable - the reproduction does not require a data set
Did you include all code required to reproduce the issue?
Did you include all relevant configuration to reproduce the issue?