- 
                Notifications
    You must be signed in to change notification settings 
- Fork 338
ci: Migrate to uv for python #1796
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Signed-off-by: Xuanwo <github@xuanwo.io>
Signed-off-by: Xuanwo <github@xuanwo.io>
Signed-off-by: Xuanwo <github@xuanwo.io>
Signed-off-by: Xuanwo <github@xuanwo.io>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! awesome ci time improvements.
a couple of nits
| name = "pyiceberg-core" | ||
| readme = "project-description.md" | ||
| requires-python = "~=3.9" | ||
| requires-python = ">=3.10,<3.13" | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| requires-python = ">=3.10,<3.13" | |
| requires-python = ">=3.10" | 
nit: do we have to use upperbound?
| "maturin>=1.0,<2.0", | ||
| "pytest>=8.3.2", | ||
| "datafusion==50.*", | ||
| "pyiceberg[sql-sqlite,pyarrow] @ git+https://github.com/apache/iceberg-python.git@d3eb149fe99b14e714a06e727b69cd617c6c052d", | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why are we using this specific commit?
| - name: Install uv | ||
| shell: bash | ||
| run: | | ||
| python -m pip install uv==0.9.3 | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| - name: Install uv | |
| shell: bash | |
| run: | | |
| python -m pip install uv==0.9.3 | |
| - name: Install uv | |
| uses: astral-sh/setup-uv@v6 | |
| with: | |
| version: "0.9.3" | 
nit: recommend to use the setup-uv action, https://docs.astral.sh/uv/guides/integration/github/#installation
| uv sync --group dev | ||
| ``` | ||
|  | ||
| ## Build | ||
|  | ||
| ```shell | ||
| hatch run dev:develop | ||
| uv run --group dev maturin develop | ||
| ``` | ||
|  | ||
| ## Test | ||
|  | ||
| ```shell | ||
| hatch run dev:test | ||
| uv run --group dev pytest | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it would be helpful to add these into a Makefile
| uv rocks! | 
## Which issue does this PR close? <!-- We generally require a GitHub issue to be filed for all bug fixes and enhancements and this helps us generate change logs for our releases. You can link an issue to this PR using the GitHub syntax. For example `Closes #123` indicates that this PR will close issue #123. --> - Closes #. ## What changes are included in this PR? <!-- Provide a summary of the modifications in this PR. List the main changes such as new features, bug fixes, refactoring, or any other updates. --> Follow up to #1796 This PR adds ``` make install make build make test ``` to `bindings/python/` ## Are these changes tested? <!-- Specify what test covers (unit test, integration test, etc.). If tests are not included in your PR, please explain why (for example, are they covered by existing tests)? -->


Which issue does this PR close?
What changes are included in this PR?
Migrate to uv
Are these changes tested?