[PD1-240] - migrate from poetry to uv for dependency management

[olivierpichon]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request undertakes a significant change by migrating the project's Python dependency management from Poetry to uv. This transition streamlines dependency resolution and installation processes, leading to potentially faster development workflows and more efficient project setup. The changes involve updating configuration files and documentation to align with the new tool.

Highlights

• Dependency Management Migration: The project's dependency management system has been migrated from Poetry to uv, aiming for faster and more efficient package operations.
• Configuration Updates: Project configuration files, including .claude/settings.json and pyproject.toml, were updated to reflect the switch to uv.
• Documentation Refresh: The README.md file was revised to provide accurate installation, usage, and development instructions for users leveraging uv.

Changelog

• .claude/settings.json
  • Updated command hooks to use 'uv run' instead of 'poetry run'.
• README.md
  • Replaced 'poetry' references with 'uv' in installation, usage, and development sections.
  • Updated command examples to use 'uv add' and 'uv sync'.
• poetry.lock
  • Removed the Poetry lock file.
• pyproject.toml
  • Migrated build system configuration from Poetry to Hatchling.
  • Restructured development dependencies to use 'dependency-groups' instead of 'tool.poetry.group.dev.dependencies'.
• uv.lock
  • Added the new uv lock file, reflecting the project's dependencies managed by uv.

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/ci.yml

Activity

• No human activity (comments, reviews) has been recorded on this pull request yet.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request aims to migrate the project from Poetry to uv for dependency management. The changes correctly update configuration files like pyproject.toml, .claude/settings.json, and README.md, and replace poetry.lock with uv.lock.

However, the migration is critically incomplete. The Python source files for the hooks still contain hardcoded calls to poetry, which will cause them to fail in an environment without Poetry installed. This defeats the purpose of the migration.

The following files must be updated to replace poetry run with uv run:

• src/python_claude/hooks/ruff_format_hook.py
• src/python_claude/hooks/ruff_check_hook.py
• src/python_claude/hooks/mypy_hook.py
• src/python_claude/hooks/pytest_hook.py
• src/python_claude/hooks/session_start_hook.py (in the help text)

These changes are essential for the project to function correctly after the migration.