Writing Mercurial extensions

Mercurial features an extension mechanism for adding new commands.

Extensions allow the creation of new features and using them directly from the main hg command line as if they were builtin commands. The extensions have full access to the MercurialApi.

Writing your own extension

File Layout

Extensions are usually written as simple python modules. Larger ones are better split into multiple modules of a single package (see ConvertExtension). The package root module gives its name to the extension and implements the cmdtable and optional callbacks described below.

Command table

To write your own extension, your python module can provide an optional dict named cmdtable with entries describing each command.

The `cmdtable` dictionary

The cmdtable dictionary uses as key the new command names, and, as value, a tuple containing:

1. the function name to be called when the command is used.
2. a list of options the command can take.
3. a help string for the command.

List of options

Al the command flag options are documented in the mercurial/fancyopts.py sources.

The options list is a list of tuples containing:

1. a flag specifying if the option is of the short or long sort, like -o or --option.

2. an option name.
3. a default value for the option.
4. a help string for the option.

Example `cmdtable`

cmdtable = {
    # "command-name": (function-call, options-list, help-string)
    "print-parents": (print_parents,
                     [('s', 'short', None, 'print short form'),
                      ('l', 'long', None, 'print long form')],
                     "hg print-parents [options] node")
}

Command function signatures

Functions that implement new commands always receive a ui and usually a repo parameter. Please see the MercurialApi for information on how to use these. The rest of parameters are taken from the command line items that don't start with a dash and are passed in the same order they were written. If no default value is given in the parameter list they are required.

If there is no repo to be associated with the command and consequently no repo passed then commands should be imported from mercurial and the extension name should be added to commands.norep like this:

from mercurial import commands
...
commands.norepo += " mycommand" 

For examples of norepo see the source code to the RcpathExtension (direct link to attachment:RcpathExtension/rcpath.py extension source) or the ConvertExtension (direct link to [http://hg.intevation.org/mercurial/crew/file/f5f6b7dcd217/hgext/convert/__init__.py#l186 convert] extension source).

Extension setup

Extensions can implement an optional callback named extsetup. It is called after all the extension are pre-loaded, and can be useful in case one extension optionally depends on another extension.

Signature:

def extsetup():
    # ...

Repository setup

Extensions can implement an optional callback named reposetup. It is called after the main Mercurial repository initialization, and can be used to setup any local state the extension might need.

As other command functions it receives an ui object and a repo object (no additional parameters for this, though):

def reposetup(ui, repo):
    #do initialization here.

Example extension

   1 #!/usr/bin/env python
   2 
   3 from mercurial import hg
   4 
   5 # every command must take a ui and and repo as arguments.
   6 # opts is a dict where you can find other command line flags
   7 #
   8 # Other parameters are taken in order from items on the command line that
   9 # don't start with a dash.  If no default value is given in the parameter list,
  10 # they are required.
  11 # 
  12 # For experimenting with Mercurial in the python interpreter: 
  13 # Getting the repository of the current dir: 
  14 #    >>> from mercurial import hg, ui
  15 #    >>> repo = hg.repository(ui.ui(), path = ".")
  16 
  17 def printparents(ui, repo, node, **opts):
  18     # The doc string below will show up in hg help
  19     """Print parent information"""
  20 
  21     # repo can be indexed based on tags, an sha1, or a revision number
  22     ctx = repo[node]
  23     parents = ctx.parents()
  24 
  25     if opts['short']:
  26         # the string representation of a context returns a smaller portion of the sha1
  27         print "short %s %s" % (str(parents[0]), srt(parents[1]))
  28     elif opts['long']:
  29         # the hex representation of a context returns the full sha1
  30         print "long %s %s" % (parents[0].hex(), parents[1].hex())
  31     else:
  32         print "default %s %s" % (str(parents[0]), str(parents[1]))
  33 
  34 cmdtable = {
  35     # cmd name        function call
  36     "print-parents": (printparents,
  37                      # see mercurial/fancyopts.py for all of the command
  38                      # flag options.
  39                      [('s', 'short', None, 'print short form'),
  40                       ('l', 'long', None, 'print long form')],
  41                      "[options] REV")
  42 }

If cmdtable or reposetup is not present, your extension will still work. This means that an extension can work "silently", without making new functionality directly visible through the command line interface.

Where to put extensions in the source tree

As of a change shortly after the 0.7 release, the recommended location for installing extensions in the source tree is the hgext directory. If you put a file in there called foo.py, you will need to refer to it in the hgrc file as a qualified package name, hgext.foo.

The contents of the hgext directory will be installed by the top-level setup.py script along with the rest of Mercurial.

See CategoryExtension for related pages and ["UsingExtensions"] for a list of readily avaliable extensions bundled with Mercurial or provided by third parties.

CategoryExtension CategoryHowTo CategoryInternals