Skip to content

Migrate to uv and Ruff #5788

Open
Open
Migrate to uv and Ruff#5788
Assignees
franciscojavierarceo
Labels
good first issueGood for newcomerskind/featureNew feature or requeststarter-ticketGood starter tickets

Description

@franciscojavierarceo
franciscojavierarceo
opened on Dec 19, 2025

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

  1. franciscojavierarceo
    added
    kind/featureNew feature or request
    on Dec 19, 2025
  2. ntkathole
    added
    good first issueGood for newcomers
    starter-ticketGood starter tickets
    on Dec 19, 2025

  3. YassinNouh21 commented on Jan 4, 2026

    @YassinNouh21
    YassinNouh21
    on Jan 4, 2026
    Collaborator

    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:

    1. Full uv project management - Replace setuptools with uv as the build/project manager (uv.lock, uv run, pyproject.toml-based deps)?
    2. Complete legacy cleanup - Remove remaining pip/piptools commands and ensure all CI uses uv?
    3. Expand Ruff rules - Enable additional linting rules (e.g., B, C4, UP, SIM) and remove any other linters?
    4. All of the above?

    This will help me create a proper implementation plan. Thanks!

  4. franciscojavierarceo
    self-assigned this
    on Feb 18, 2026

  5. Sagargupta16 commented on Mar 4, 2026

    @Sagargupta16
    Sagargupta16
    on Mar 4, 2026
    Contributor

    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!

  6. franciscojavierarceo commented on Mar 5, 2026

    @franciscojavierarceo
    franciscojavierarceo
    on Mar 5, 2026
    MemberAuthor

    Hi @Sagargupta16 I've been incrementally working on this!

    most recently #5957 which i forgot to link in the PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

good first issueGood for newcomerskind/featureNew feature or requeststarter-ticketGood starter tickets

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions