Hotfix: Pin python duckdb to 1.3.2#170
Merged
Merged
Conversation
Why these changes are being introduced: The duckdb python client recently released 1.4.0. It has some exciting new features that we can utilize, but it introduces some minor changes that conflict with another 3rd party library, duckdb_engine, that we use for creating a SQLAlchemy engine object from a DuckDB connection. While upgrading to 1.4.0 will be a net positive for us, we are utilizing this library heavily in other contexts. How this addresses that need: Pins our python duckdb client to previous release 1.3.2, which maintains current functionality. A new ticket will be created to work through the 1.4.0 upgrade. Side effects of this change: * None Relevant ticket(s): * None
ehanson8
approved these changes
Sep 17, 2025
Pull Request Test Coverage Report for Build 17799898207Details
💛 - Coveralls |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose and background context
Why these changes are being introduced:
The
duckdbpython client recently released 1.4.0. It has some exciting new features that we can utilize, but it introduces some minor changes that conflict with another 3rd party library,duckdb_engine, that we use for creating a SQLAlchemy engine object from a DuckDB connection.While upgrading to 1.4.0 will be a net positive for us, we are utilizing this library heavily in other contexts.
How this addresses that need:
Pins our python
duckdbclient to previous release 1.3.2, which maintains current functionality. A new ticket will be created to work through the 1.4.0 upgrade.Includes new or updated dependencies?
YES
Changes expectations for external applications?
NO
What are the relevant tickets?