pyproject-modern-python

Migrating from setup.py to pyproject.toml involves centralizing your project metadata using PEP 621 standards. This skill configures the new file, replaces legacy scripts with hatchling builds, and sets up a src-layout package structure automatically.

Configuring hatchling with hatch-vcs enables modern Python builds driven by Git-based versioning. This skill sets up the build backend in pyproject.toml, linking your project version dynamically to Git tags for automated release tagging.

Yes, pyproject.toml supports uv lockfile management for deterministic CI environments. This skill integrates uv to generate lockfiles, manage optional dependencies, and configure dependency-groups to ensure consistent testing and packaging pipelines.

A src-layout package structure is needed to prevent import errors during testing and ensure clean package builds. This skill configures the src-layout within your pyproject.toml, separating source code from project root to avoid accidental local imports.

You can define optional dependencies and dependency-groups directly in pyproject.toml using PEP 621 metadata. This skill structures these dependency configurations, allowing precise environment management for development and production contexts.

PEP 621 metadata provides a standardized, declarative way to define project information in pyproject.toml, replacing imperative setup.py scripts. This approach centralizes configuration, simplifies maintenance, and ensures compatibility with modern build tools like hatchling.