Glossary¶
packaging.python.org
This PEP proposes a collection of changes related to the upload and distribution of digitally signed attestations and metadata used to verify them on a Python package repository, such as PyPI.
This PEP defines a specification how licenses are documented in the Python projects.
Summary of discussions: We requested the Packaging community for feedback on the proposed survey questions The Python Packaging Survey was conducted in Sept-Oct. The results are summarized here. We asked maintainers/contributors on which they would like to discuss the Packaging Strategy. The most popular option was Discourse. The first part of strategy discussion was about unification of Packaging tools Discussion cue: In the Packaging survey, users indicated that they were looking for mor...
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 the project section is specified
In late March, version 78.0.1 of Setuptools — an important Python packaging tool — was released [...]
In late March, version 78.0.1 of Setuptools — an important Python packaging tool — was released [...]
Introduction The Release Manager(s) (RM) for Ansible Community Package, are always the Ansible Community Team members, who are Red Hatters. But with this endeavor we are trying to open up the relea...
there's no Zen here
This PEP proposes a Python Packaging Council with broad authority over packaging standards, tools, and implementations. Like the Python Steering Council, the Packaging Council seeks to exercise this authority as rarely as possible; instead, they use thi...
Happy new year to all. Today's post is about a folder on my desktop named dev. It's where I've kept (for many years, well into my Windows-using days, even into the era when I used SVN rather than Git)