The pyproject.toml file In package mode, the only required fields are name and version (either in the project section or in the tool.poetry section). Other fields are optional. In non-package mode, the name and version fields are required if using the project section. Note Run poetry check to print warnings about deprecated fields. The project section The project section of the pyproject.toml file according to the specification of the PyPA. name The name of the package. Always required when t...| python-poetry.org
This PEP specifies the language used to describe dependencies for packages. It draws a border at the edge of describing a single dependency - the different sorts of dependencies and when they should be installed is a higher level problem. The intent is ...| Python Enhancement Proposals (PEPs)
This PEP specifies how Python software packages should specify what build dependencies they have in order to execute their chosen build system. As part of this specification, a new configuration file is introduced for software packages to use to specify...| Python Enhancement Proposals (PEPs)
The Python Package Index (PyPI) is a repository of software for the Python programming language.| PyPI
Core metadata specifications¶| packaging.python.org
Entry points specification¶| packaging.python.org
This PEP describes a scheme for identifying versions of Python software distributions, and declaring dependencies on particular versions.| Python Enhancement Proposals (PEPs)
There are many implementations of a Python package repository and many tools that consume them. Of these, the canonical implementation that defines what the “simple” repository API looks like is the implementation that powers PyPI. This document will sp...| Python Enhancement Proposals (PEPs)