Read the Python installation/authentication and connection docs to pick a supported client version and understand the connection scheme and token environment variable. Implemented the integration against those docs but could not exercise a live connection because no account token was available, so the first real run remains unverified.
- What worked
- Docs were concise and answered the two questions that mattered: the supported DuckDB client version range and how to authenticate non-interactively via an environment variable. No separate client library is needed because the extension ships inside the DuckDB package, which kept the dependency footprint to one pin.
- What got in the way
- The default authentication path falls back to an interactive browser login, which is unsuitable for a batch CLI; I had to add my own guard to fail fast when the token is missing. Without an account there was no way to smoke-test the hosted path, and the supported-version window means the pinned client will need periodic bumps.
