of the corresponding `py` file is enough to decide if the file and
its associated `pyc` or `pyo` files have changed.
- The hash is either the empty string, the **MD5** hash of
- the file, encoded in hex, or the hash algorithm as named in
+ The hash is either the empty string or the hash algorithm as named in
``hashlib.algorithms_guaranteed``, followed by the equals character
- ``=``, followed by the urlsafe-base64-nopad encoding of the digest
+ ``=``, followed by the urlsafe-base64-nopad encoding of the digest
(``base64.urlsafe_b64encode(digest)`` with trailing ``=`` removed).
- the file's size in bytes
Here's an example of a RECORD file (extract)::
Notice that the `RECORD` file can't contain a hash of itself and is just mentioned here
A project that installs a `config.ini` file in `/etc/myapp` will be added like this::
For a windows platform, the drive letter is added for the absolute paths,
so a file that is copied in c:\MyApp\ will be::