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)
The .dist-info directory¶| packaging.python.org
Specification¶| packaging.python.org
pip 25.0 adds support for SPDX License Expressions (PEP 639), build environment bugfixes, and further optimizations among other changes.| Richard Si
pip 24.3 is a small release with a truststore bugfix, QoL improvements, and one minor deprecation of noncompliant wheel filenames.| ichard26.github.io
What's in a name?| blog.deps.dev
Writing your pyproject.toml#| packaging.python.org
ENOSUCHBLOG| blog.yossarian.net
Two years since PEP 665 was rejected and three years since I started working towards some lock file solution, I present my next (and last regardless of outcome) attempt at coming up with a lock file standard. Terms “platform”: OS plus CPU “environment”: interpreter plus platform “distribution”: in the PyPA spec sense, i.e. a project “lock entry”: a set of distribution files locked for a specific environment “lock file”: a set of lock entries for a specific set of dependenc...| Discussions on Python.org
Declaring project metadata: the [project] table¶| packaging.python.org
Version numbers are hard to get right. Semantic Versioning (SemVer) communicates backward compatibility via version numbers which often lead to a false sense of security and broken promises.| jacobtomlinson.dev
Specification#| packaging.python.org
Description¶| pip.pypa.io
File Format¶| packaging.python.org
Binary Distribution¶A specific kind of Built Distribution that contains compiled| packaging.python.org
Core metadata specifications¶| packaging.python.org
Description¶| pip.pypa.io