From 1d8558c0db87c75e2a571b882d0623bf9c5e9f93 Mon Sep 17 00:00:00 2001 From: Alex Malins Date: Tue, 7 Jan 2025 23:55:41 +0900 Subject: [PATCH] Restore harlequin-databricks as optional dep 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) https://github.com/databricks/databricks-sql-python/pull/452 --- pyproject.toml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pyproject.toml b/pyproject.toml index 5cea95c..9a19113 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -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 }