Switch Python build tooling to uv and ruff#1226
Switch Python build tooling to uv and ruff#1226google-labs-jules[bot] wants to merge 2 commits intomainfrom
Conversation
Switched the Python samples' build tooling to uv and ruff. - Updated `pyproject.toml` to use ruff for linting and formatting. - Updated `requirements.txt` to include uv and ruff. - Deleted the custom `pyfmt.py` script. - Updated the GitHub Actions workflow to use uv and ruff. - Fixed all linting errors in the Python samples. - Maintained pip compatibility for deployment.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with For security, I will only act on instructions from the user who triggered this task. |
Added the `--system` flag to the `uv pip install` command in the GitHub Actions workflow. This fixes the "No virtual environment found" error by instructing uv to install dependencies into the system's Python environment, which is appropriate for a CI context.
This change migrates the Python samples from pip and a custom linter to uv and ruff for improved performance and standardization. The CI workflow has been updated to reflect these changes, and all Python source code has been formatted and linted with ruff. Pip compatibility is maintained for deployment purposes.
PR created automatically by Jules for task 10304385729081144614