This PEP proposes a new file format for specifying dependencies to enable reproducible installation in a Python environment. The format is designed to be human-readable and machine-generated. Installers consuming the file should be able to calculate wha...| Python Enhancement Proposals (PEPs)
Last time, we built a hybrid concurrent.futures executor using inheritance. Today, we're building it again (twice!) using composition and functions only, to figure out which way is better and why. Consider this a worked example.| death and gravity
This PEP proposes extending the core metadata specification for Python packaging to include a new, repeatable field named Import-Name to record the import names that a project owns once installed. A new key named import-names will be added to the [proje...| Python Enhancement Proposals (PEPs)
This PEP defines a specification how licenses are documented in the Python projects.| Python Enhancement Proposals (PEPs)
The .dist-info directory¶| packaging.python.org
Settings| docs.astral.sh
Base HTML API#| packaging.python.org
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
Declaring project metadata: the [project] table¶| packaging.python.org
This PEP specifies how to write a project’s core metadata in a pyproject.toml file for packaging-related tools to consume.| Python Enhancement Proposals (PEPs)
Binary Distribution¶A specific kind of Built Distribution that contains compiled| packaging.python.org
Entry points specification¶| packaging.python.org