chore: migrate from Poetry to uv - #236
Open
Tobias Cadée (tobiascadee) wants to merge 4 commits into
Open
Conversation
…abase feat: Automatically create databases
- Replace Poetry-based pyproject.toml with PEP 621 project metadata - Use uv as the build backend with uv_build - Move dev dependencies to dependency-groups - Replace poetry.lock with uv.lock - Move clickhouse-sqlalchemy git source to [tool.uv.sources]
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
1 participant
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.
Summary
Migrate the project's build tooling from Poetry to uv.
Changes
[tool.poetry]format to PEP 621[project]metadatapoetry-corewithuv_build[tool.poetry.dev-dependencies]to[dependency-groups]clickhouse-sqlalchemygit dependency to[tool.uv.sources]poetry.lockwithuv.lockWhy
uv provides significantly faster dependency resolution and installation, and uses the standard PEP 621 project metadata format.