-
Notifications
You must be signed in to change notification settings - Fork 0
Moving from poetry to uv. #21
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
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.
Pull Request Overview
This PR migrates the project's dependency management from Poetry to uv, modernizing the toolchain with a faster Python package installer and resolver.
- Replaces Poetry configuration with standard Python packaging (
pyproject.tomlusingprojecttable) - Updates build system from Poetry to Hatchling
- Migrates CI/CD workflow and Makefile to use uv commands
Reviewed Changes
Copilot reviewed 5 out of 8 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| pyproject.toml | Complete migration from Poetry format to standard Python packaging with uv/hatchling |
| .github/workflows/test.yaml | Updates CI workflow to use uv for dependency installation and testing |
| Makefile | Replaces Poetry commands with uv equivalents and adds comprehensive task automation |
| tests/test_transformer_model.py | Minor code formatting improvement for type annotation |
| tests/test_data_processor.py | Removes unused Any import from typing |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
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.
Pull Request Overview
Copilot reviewed 19 out of 31 changed files in this pull request and generated 3 comments.
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
Describe your changes
Provide a clear and concise description of the changes made in this pull request. Include any relevant context or background information.
Issue ticket number and link
Type of Change
Check the type of change your pull request introduces:
Checklist before requesting a review
Before submitting your pull request, ensure the following: