Skip to content

[Feature] vendor dldb 1.0.0 with pinned lance stack for public installs - #2

Draft
Fantasy97 wants to merge 1 commit into
AI45Lab:masterfrom
Fantasy97:feat/vendor-dldb-one-commit
Draft

[Feature] vendor dldb 1.0.0 with pinned lance stack for public installs#2
Fantasy97 wants to merge 1 commit into
AI45Lab:masterfrom
Fantasy97:feat/vendor-dldb-one-commit

Conversation

@Fantasy97

Copy link
Copy Markdown

Summary

  • Vendor upstream dldb as packages/dldb (dldb==1.0.0, runtime core only).
  • Remove the private Gitee git dependency; default installs use the in-repo package (uv path source / pip editable ./packages/dldb).
  • Pin the Lance stack in dldb to reduce cross-environment nested-trajectory read failures.

Compatibility guidance

Writer/reader compatibility is primarily gated by lancedb / pylance. This PR constrains dldb to the validated band: Python >=3.10,<3.13, lancedb>=0.34,<0.35, pylance>=9,<10, plus pandas/pyarrow ranges. Keep writer and reader on the same Lance generation; reinstall existing envs after upgrading; validate nested R/W before bumping Lance majors.

Updating dldb later

  • In-repo default: update packages/dldb, bump its version/pins, then uv pip install -e ".[dev]" (or pip: install ./packages/dldb then ".[dev]").
  • Explicit GitHub override: pip install -U "dldb @ git+https://github.com/<org>/dldb.git@v1.0.0" then pip install -e ".[dev]".

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