Skip to main content

Mercurial Fingerprint Plugin

The hg-fingerprint mercurial plugin does two things:

  1. Enhances the archive command with options to control the .hg_archival.txt file in the following ways:

    • Allow multiple fingerprint files to be specified,

    • Adjust the file name(s) thereof,

    • Change the file format(s), and

    • Add a timestamp for when the archive was generated.

  2. Provides the fingerprint command to output the archive fingerprint file without having to actually do the archive.

Project

Supported Formats

The following formats are supported:

  • text (the default):

    repo: dca7d15bf04445e0a3136d5ce5cfa034e5cfa034
    node: 6d881282ad46412ead8ad83e074ce451074ce451
    branch: default
    latesttag: blue
    latesttag: moon
    latesttagdistance: 7
    timestamp: 2009-02-13T23:31:30Z
  • json (whitespace added for clarity):

    {
      "repo": "dca7d15bf04445e0a3136d5ce5cfa034e5cfa034",
      "node": "6d881282ad46412ead8ad83e074ce451074ce451",
      "branch": "default",
      "latesttags": ["blue", "moon"],
      "latesttagdistance": 7,
      "timestamp": "2009-02-13T23:31:30Z"
    }
  • yaml:

    repo: dca7d15bf04445e0a3136d5ce5cfa034e5cfa034
    node: 6d881282ad46412ead8ad83e074ce451074ce451
    branch: default
    latesttags: [blue, moon]
    latesttagdistance: 7
    timestamp: '2009-02-13T23:31:30Z'
  • xml (whitespace added for clarity):

    <?xml version='1.0' encoding='UTF-8'?>
    <fingerprint>
      <repo>dca7d15bf04445e0a3136d5ce5cfa034e5cfa034</repo>
      <node>6d881282ad46412ead8ad83e074ce451074ce451</node>
      <branch>default</branch>
      <latesttag>blue</latesttag>
      <latesttag>moon</latesttag>
      <latesttagdistance>7</latesttagdistance>
      <timestamp>2009-02-13T23:31:30Z</timestamp>
    </fingerprint>

Options

The fingerprint plugin adds the following new configuration section:

[fingerprint]

path                    = .hg_archival.txt
format                  = text
timestamp               = true
  • path : ( str | list(str) ), default: ‘.hg_archival.txt’

    The path, within the archive, to store the fingerprint in. The results are undefined if the path already exists. The path may specify multiple locations (separated and escaped using shell escape syntax).

  • format : ( str | list(str) ), default: ‘auto’

    The file format to store the fingerprint in. Can be any of the above listed formats, plus the special value auto, which specifies that the mime-type (based on extension) of the path should be used. If the path specifies multiple locations, then format can also be a list. If there are more paths than formats, the last format is used.

  • timestamp : bool, default: true

    Whether or not to store the archive generation timestamp in the fingerprint in ISO 8601 date-time format. Note that this is the only value whose default alters the standard way the archive command works – this is because it is additive, and should therefore have no, or at most minimal, impact.

Metadata

Release files for hg_fingerprint 0.1.6

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for hg_fingerprint 0.1.6
File Size Uploaded Provenance
hg_fingerprint-0.1.6.tar.gz 10.7 kB Without provenance Details

Release files / hg_fingerprint-0.1.6.tar.gz

Download URL hg_fingerprint-0.1.6.tar.gz
Size 10.7 kB
Tags Source
SHA-256 checksum
How to use checksums
addb60c3aa6ea6e2cb886219d56909db0bc9f9e44853210f9f4eff40bd72c694
BLAKE2b-256 checksum
How to use checksums
bb2743dc55289f784493c3d271a4f7899877be5584dba365f7cb8b726d2286c3
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via Python-urllib/3.8

Security for hg_fingerprint 0.1.6

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page