Thanks for the PR!

I don't quite follow what this PR enables - can you not already assign the default connection like so?

import duckdb
duckdb.default_connection = duckdb.connect()

If that does not work, could we not make that work instead of changing the API?

Thanks for the PR!

I don't quite follow what this PR enables - can you not already assign the default connection like so?

import duckdb
duckdb.default_connection = duckdb.connect()

If that does not work, could we not make that work instead of changing the API?

It doesn't work, and we can't make that work.
default_connection is an attribute which is assigned the value of DuckDBPyConnection::DefaultConnection() at the import of the module

If a new value is assigned to that, it does not reflect on the internals of the module

I also explained this in the Incompatible change section of the description

There might be some way we can look up the current value of the default_connection attribute, but that would need to go through Python every time, and we wouldn't be able to protect it against arbitrary object assignation

I would also vote for removing duckdb.default_connection entirely in favor of duckdb.connect(':default:')
Perhaps set_default_connection could be DuckDBPyConnection::set_as_default instead?

Thanks!