What problem it solves

Python projects often spread their packaging and dependency metadata across several files such as setup.py, requirements.txt, setup.cfg, MANIFEST.in and Pipfile, which makes the dependency stack harder to keep consistent. Poetry consolidates that metadata so a project declares its dependencies and stack in one place, ensuring the right stack everywhere.

Key features

• Single-file project format — Project metadata and dependencies live in a simple pyproject.toml, replacing the usual collection of setup.py, requirements.txt, setup.cfg, MANIFEST.in and Pipfile files.

  Source: README, pyproject.toml

• Rich dependency specification — Dependencies can carry version constraints, extras, prereleases, Python version markers and git references, all expressed in the project file.

  Source: README

• Dependency groups — Dependencies can be organised into groups such as dev and docs, with groups marked optional and installed only when explicitly requested.

  Source: README

• Package metadata and scripts — Standard project metadata such as name, version, license, authors, keywords and console scripts is declared directly in the project file, following the pyproject.toml format.

  Source: README

• Multiple installation methods — The tool can be installed through several methods, including a simple script, with further guidance covering alternate methods and CI usage in the installation documentation.

  Source: README, docs

Who it may suit

Inference: this may suit Python developers who maintain libraries or applications and want packaging plus dependency declarations kept in one file, as well as teams standardising on a single project format.

Topics to discuss

• How do you organise dependency groups such as dev and docs so that optional groups stay out of production installs?

• Which version constraint syntax do you prefer in practice, PEP 621 style or the Poetry-specific form, and why?

• What migration path do you recommend for projects currently using setup.py, requirements.txt or Pipfile?

Written by ReadmeX AI from the project's README, source and public GitHub data; it may contain mistakes.

Read the original README https://github.com/python-poetry/poetry#readme

ReadmeX opened this community for a trending project; it is not run by the project. Maintainers can claim it from the community page.