Recording installed projects¶
This document specifies a common format of recording information about Python projects installed in an environment. A common metadata format allows tools to query, manage or uninstall projects, regardless of how they were installed.
Almost all information is optional. This allows tools outside the Python ecosystem, such as Linux package managers, to integrate with Python tooling as much as possible. For example, even if an installer cannot easily provide a list of installed files in a format specific to Python tooling, it should still record the name and version of the installed project.
History and change workflow¶
The metadata described here was first specified in PEP 376, and later amended in PEP 627. It was formerly known as Database of Installed Python Distributions. Further amendments (except trivial language or typography fixes) must be made through the PEP process (see PEP 1).
While this document is the normative specification, these PEPs that introduce changes to it may include additional information such as rationales and backwards compatibility considerations.
The .dist-info directory¶
Each project installed from a distribution must, in addition to files,
install a “
.dist-info” directory located alongside importable modules and
packages (commonly, the
This directory is named as
Distribution versions fields corresponding to Core metadata specifications.
The name field must be in normalized form (see PEP 503
for the definition of normalization).
.dist-info directory can contain these files, described in detail
METADATA: contains project metadata
RECORD: records the list of installed files.
INSTALLER: records the name of the tool used to install the project.
METADATA file is mandatory.
All other files may be omitted at the installing tool’s discretion.
Additional installer-specific files may be present.
The Binary distribution format specification describes additional
files that may appear in the
.dist-info directory of a Wheel.
Such files may be copied to the
.dist-info directory of an
The previous versions of this specification also specified a
file. This file is now considered a tool-specific extension, but may be
standardized again in the future. See PEP 376
for its original meaning.
The METADATA file¶
METADATA file contains metadata as described in the Core metadata specifications
specification, version 1.1 or greater.
METADATA file is mandatory.
If it cannot be created, or if required core metadata is not available,
installers must report an error and fail to install the project.
The RECORD file¶
RECORD file holds the list of installed files.
It is a CSV file containing one record (line) per installed file.
The CSV dialect must be readable with the default
reader of Python’s
"(straight double quote),
line terminator: either
Each record is composed of three elements: the file’s path, the hash of the contents, and its size.
The path may be either absolute, or relative to the directory containing
.dist-info directory (commonly, the
On Windows, directories may be separated either by forward- or backslashes
The hash is either an empty string or the name of a hash algorithm from
hashlib.algorithms_guaranteed, followed by the equals character
the digest of the file’s contents, encoded with the urlsafe-base64-nopad
base64.urlsafe_b64encode(digest) with trailing
The size is either the empty string, or file’s size in bytes, as a base 10 integer.
For any file, either or both of the hash and size fields may be left empty.
Commonly, entries for
.pyc files and the
RECORD file itself have empty
hash and size.
For other files, leaving the information out is discouraged, as it
prevents verifying the integrity of the installed project.
RECORD file is present, it must list all installed files of the
.pyc files corresponding to
.py files listed in
RECORD, which are optional.
Notably, the contents of the
.dist-info directory (including the
file itself) must be listed.
Directories should not be listed.
To completely uninstall a package, a tool needs to remove all
files listed in
.pyc files (of all optimization levels)
corresponding to removed
.py files, and any directories emptied by
Here is an example snippet of a possible
/usr/bin/black,sha256=iFlOnL32lIa-RKk-MDihcbJ37wxmRbE4xk6eVYVTTeU,220 ../../../bin/blackd,sha256=lCadt4mcU-B67O1gkQVh7-vsKgLpx6ny1le34Jz6UVo,221 __pycache__/black.cpython-38.pyc,, __pycache__/blackd.cpython-38.pyc,, black-19.10b0.dist-info/INSTALLER,sha256=zuuue4knoyJ-UwPPXg8fezS7VCrXJQrAP7zeNuwvFQg,4 black-19.10b0.dist-info/LICENSE,sha256=nAQo8MO0d5hQz1vZbhGqqK_HLUqG1KNiI9erouWNbgA,1080 black-19.10b0.dist-info/METADATA,sha256=UN40nGoVVTSpvLrTBwNsXgZdZIwoKFSrrDDHP6B7-A0,58841 black-19.10b0.dist-info/RECORD,, black.py,sha256=45IF72OgNfF8WpeNHnxV2QGfbCLubV5Xjl55cI65kYs,140161 blackd.py,sha256=JCxaK4hLkMRwVfZMj8FRpRRYC0172-juKqbN22bISLE,6672 blib2to3/__init__.py,sha256=9_8wL9Scv8_Cs8HJyJHGvx1vwXErsuvlsAqNZLcJQR0,8 blib2to3/__pycache__/__init__.cpython-38.pyc,, blib2to3/__pycache__/pygram.cpython-38.pyc,sha256=zpXgX4FHDuoeIQKO_v0sRsB-RzQFsuoKoBYvraAdoJw,1512 blib2to3/__pycache__/pytree.cpython-38.pyc,sha256=LYLplXtG578ZjaFeoVuoX8rmxHn-BMAamCOsJMU1b9I,24910 blib2to3/pygram.py,sha256=mXpQPqHcamFwch0RkyJsb92Wd0kUP3TW7d-u9dWhCGY,2085 blib2to3/pytree.py,sha256=RWj3IL4U-Ljhkn4laN0C3p7IRdfvT3aIRjTV-x9hK1c,28530
RECORD file is missing, tools that rely on
.dist-info must not
atempt to uninstall or upgrade the package.
(This does not apply to tools that rely on other sources of information,
such as system package managers in Linux distros.)
The INSTALLER file¶
INSTALLER is a single-line text file naming the tool used to
install the project.
If the installer is executable from the command line,
should contain the command name.
Otherwise, it should contain a printable ASCII string.
The file can be terminated by zero or more ASCII whitespace characters.
Here are examples of two possible
MegaCorp Cloud Install-O-Matic
This value should be used for informational purposes only.
For example, if a tool is asked to uninstall a project but finds no
file, it may suggest that the tool named in
INSTALLER may be able to do the
The direct_url.json file¶
This file MUST be created by installers when installing a distribution from a requirement specifying a direct URL reference (including a VCS URL).
This file MUST NOT be created when installing a distribution from an other type of requirement (i.e. name plus version specifier).
Its detailed specification is at Recording the Direct URL Origin of installed distributions.