GeezerVison is showing github.com — Migrate to uv and Ruff · Issue #5788 · feast-dev/feast
Migrate to uv and Ruff #5788
Description
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
Activity
YassinNouh21 commented on Jan 4, 2026
Hi @franciscojavierarceo! I'd like to work on this issue, but I noticed the codebase already uses both uv and Ruff to some extent:
Current uv usage:
uv pip compile for dependency locking (generates requirements files with hashes)
uv pip sync for installation in Makefile targets
Current Ruff usage:
- Configured in
pyproject.toml with rules ["E","F","W","I"]
- Used in
make format-python and make lint-python
Could you clarify the scope of this migration? For example:
- Full uv project management - Replace setuptools with uv as the build/project manager (uv.lock,
uv run, pyproject.toml-based deps)?
- Complete legacy cleanup - Remove remaining pip/piptools commands and ensure all CI uses uv?
- Expand Ruff rules - Enable additional linting rules (e.g.,
B, C4, UP, SIM) and remove any other linters?
- All of the above?
This will help me create a proper implementation plan. Thanks!
Sagargupta16 commented on Mar 4, 2026
Hi! I noticed this is a starter ticket and I'd love to help if contributions are welcome.
I have experience migrating projects from pip/setuptools to uv, and from flake8/pylint to Ruff. I can help with:
- Replacing
setup.py/setup.cfg with pyproject.toml (uv-compatible)
- Adding
[tool.ruff] config to pyproject.toml
- Replacing existing linter configs with Ruff equivalents
- Updating CI/CD to use
uv and ruff
Is the current assignee still working on this? Happy to pick up any remaining parts!
franciscojavierarceo commented on Mar 5, 2026
Hi @Sagargupta16 I've been incrementally working on this!
most recently #5957 which i forgot to link in the PR
Metadata
Metadata
Development
No branches or pull requestsIssue actions