python-packaging

To package a Python project using pyproject.toml, you define your project metadata and build-system requirements within the file. This approach replaces traditional setup.py configurations, applying modern PEP 517/518 and PEP 621 standards to generate reliable wheels and sdist distributions.

The best way to publish a Python package to PyPI involves building source and wheel distributions with a modern backend like setuptools, poetry, or hatchling, then uploading them via a structured publishing workflow to ensure consistent and reliable releases.

You need a build backend like setuptools, poetry, or hatchling to build a Python wheel. The Skill guides you through selecting a suitable backend defined in your pyproject.toml to automate the generation of distributable wheel files.

To distribute a CLI tool as a Python package, you configure entry points in your pyproject.toml metadata. This maps command-line scripts to specific functions in your project, allowing users to run the tool directly after installation.

Namespace packages in Python packaging allow you to split a single logical package across multiple separate distributions. The Skill provides clear folder layout strategies to implement these namespace packages effectively while maintaining modern metadata standards.

Python package builds fail with PEP 517 errors when the build-system requirements in pyproject.toml are missing or misconfigured. Ensuring your declared build backend like setuptools or hatchling is properly specified resolves these build pipeline inconsistencies.