project-migrate

Migrating a Python project to uv involves updating pyproject.toml to use the hatchling build backend, configuring tox-uv compatibility, and separating docs extra dependencies. The process also standardizes ruff, mypy, coverage, and tox structures across the repository configuration files.

Removing legacy Python setup files requires identifying and eliminating setup.py, setup.cfg, requirements.txt, and tox.ini configurations to prevent conflicting tooling. This cleanup is part of migrating to a uv-based standard that consolidates dependency management into pyproject.toml.

Migrating to uv works with existing GitHub Actions CI and ReadTheDocs configurations by updating them to align with the uv-based standard. The migration targets these specific files alongside pyproject.toml and Makefile updates to ensure consistent toolchain requirements across the project.

Using uv for dependency management in older Python repositories is possible by migrating existing configurations to a uv-based standard. This works for repositories with legacy CI setups, requirements.txt files, and setup.py scripts that need modernization across build backend, testing, and documentation tooling.

Python project configuration conflicts after switching to uv typically occur because legacy files like setup.py, setup.cfg, requirements.txt, and tox.ini remain in the repository. Removing these redundant files and consolidating settings into pyproject.toml resolves the tooling conflicts.

You need to update your Python project to a uv-based standard when dependency management, CI, and documentation configurations become inconsistent or rely on legacy tooling. This applies to repositories using setup.py, requirements.txt, and older CI setups that require modernized build, testing, and lint configurations.