python-packaging

To structure a Python package for PyPI, organize source layouts, package metadata, tests, and data files around a modern pyproject.toml configuration. This ensures your library or command-line tool installs correctly in a fresh environment.

The best way to build wheels and source distributions is applying modern packaging standards to select a build backend and generate release-ready artifacts. This process includes validating artifacts before publishing to PyPI or private indexes.

Set up CLI entry points by defining them within your pyproject.toml metadata during the project structure design phase. This configuration maps command-line tool invocations directly to your package's executable Python functions.

You do not strictly need setuptools, as modern Python packaging standards support choosing the right build backend for your workflow. The skill helps evaluate your CLI tool requirements to select the appropriate backend within your pyproject.toml.

Python packages fail to install in fresh environments due to incomplete dependency declarations or improper package data configuration. Applying correct pyproject.toml metadata and source layout validation ensures all dependencies and reusable data files are properly bundled.

Yes, you can use namespace packages by configuring them correctly within your project's pyproject.toml and source layout. This approach allows you to split a single Python package across multiple separate distributions while maintaining clean metadata.