Skip to content

Commit

Permalink
Restore harlequin-databricks as optional dep
Browse files Browse the repository at this point in the history
I think the deps issues on locking could have come
from upper bounds on the pyarrow & numpy version
set by the databricks-sql-connector

Those upper bounds have gone in the latest
databricks-sql-connector release (3.7.0), which is a
requirement of the latest harlequin-databricks release
(0.5.2)

databricks/databricks-sql-python#452
  • Loading branch information
alexmalins committed Jan 7, 2025
1 parent 6f752c1 commit 1d8558c
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion pyproject.toml
Original file line number Diff line number Diff line change
Expand Up @@ -59,7 +59,7 @@ harlequin-mysql = { version = ">=0.1", optional = true }
harlequin-odbc = { version = ">=0.1", optional = true }
harlequin-bigquery = { version = "^1.0", optional = true }
harlequin-trino = { version = ">=0.1", optional = true }
# harlequin-databricks = { version = ">=0.3", optional = true }
harlequin-databricks = { version = ">=0.5.2", optional = true }
harlequin-adbc = { version = ">=0.1", optional = true }
harlequin-cassandra = { version = ">=0.1", optional = true }
harlequin-nebulagraph = { version = ">=0.1", optional = true }
Expand Down

0 comments on commit 1d8558c

Please sign in to comment.