Skip to content

Allow python-dateutil 3 and 4 - #1074

Open
itzzdev09 wants to merge 1 commit into
databricks:mainfrom
itzzdev09:allow-dateutil-3-and-4
Open

itzzdev09 wants to merge 1 commit into
databricks:mainfrom
itzzdev09:allow-dateutil-3-and-4

Conversation

@itzzdev09

Copy link
Copy Markdown

pyproject.toml pins python-dateutil = "^2.8.0", which caps it at <3. python-dateutil 3.0.0 (21 Oct) and 4.0.0 (1 Nov) are out, so databricks-sql-connector can't be installed next to packages that require them.

The connector only uses dateutil.parser.parse (in utils.py and the SEA backend's queue.py / conversion.py) to parse timestamps and link expirations, and that behaves the same in the new releases. This changes the constraint to >=2.8.0,<5. 4.0 needs Python 3.11+, so 3.10 keeps resolving to 2.x/3.x.

poetry.lock changes only in content-hash (Poetry 2.2.1, the version in its header; locked versions unchanged). Added a line under "Unreleased" in CHANGELOG.md.

Tests: pytest tests/unit on Python 3.12 gives identical results with python-dateutil 2.9.0.post0 and 4.0.0 (1393 passed, 7 skipped; the same 6 collection errors in test_kernel_async_readers.py on both on my machine).

Signed-off-by: itzzdev09 <devved90@gmail.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant