uv

[Marc-Andrieu]

Description

Summary

Use uv for package (and venv) management, everywhere (locally and in CI/CD).

Its numerous advantages have already been discussed internally; this PR description is only about the migration steps than justifying why.

Changes Made

• Remove the requirements(-dev).txt, have the dependencies in the pyproject.toml and uv.lock
• Have dependency groups for dev, optional dependencies. Handle the case of Jellyfish
• CI/CD: use uv for real (not uv pip)
  • have a caching that works
• Dockerfile: Use an alpine uv image as base, install deps using uv
  • have a caching that works
• Dependabot: use the uv ecosystem instead
• Rewrite the start of the README.md:
  • Remove Python from the prerequisites (uv as a standalone will install it)
  • Replace the 1st part about setting up a venv with installing uv as a standalone
  • Installing deps : with uv sync
  • Running the project.

Additional Notes

Following exactly what https://docs.astral.sh/uv says

Classification

Type of Change

• 🐛 Bug fix (non-breaking change which fixes an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 🔨 Refactor (non-breaking change that neither fixes a bug nor adds a feature)
• 🔧 Infra CI/CD (changes to configs of workflows)
• 💥 BREAKING CHANGE (fix or feature that require a new minimal version of the front-end)
• 😶‍🌫️ No impact for the end-users

Impact & Scope

• Core functionality changes
• Single module changes
• Multiple modules changes
• Database migrations required
• Other: change package manager & some related stuff in CI/CD

Testing

• 1. Tested this locally
• 2. Added/modified tests that pass the CI (or tested in a downstream fork)
• 3. Tested in a deployed pre-prod
• 0. Untestable (exceptionally), will be tested in prod directly

Documentation

All