Skip to main content

A library to automatically generate and run simple argparse parsers from function signatures.

Basic

Autocommand turns a function into a command-line program. It converts the function’s parameter signature into command-line arguments, and automatically runs the function if the module was called as __main__. In effect, it lets your create a smart main function.

from autocommand import autocommand

# This program takes exactly one argument and echos it.
@autocommand(__name__)
def echo(thing)
    print(thing)
$ python echo.py hello
hello
$ python echo.py -h
usage: echo [-h] thing

positional arguments:
  thing

optional arguments:
  -h, --help  show this help message and exit
$ python echo.py hello world  # too many arguments
usage: echo.py [-h] thing
echo.py: error: unrecognized arguments: world

As you can see, autocommand uses argparse to convert the signature of the function into an argument spec, which automatically handles creating a usage statement and argument parsing.

autocommand is passed __name__ to allow it to automatically run the decorated function. If __name__ == '__main__', the arguments are parsed and the function is executed. The program’s return code is taken from the return value of the function, via sys.exit.

Types

You can use a type annotation to give an argument a type. Any type (or in fact any callable) that returns an object when given a string argument can be used, though there are a few special cases that are described later. Keep in mind that argparse will catch TypeErrors raised during parsing, so you can supply a callable and do some basic argument validation as well.

@autocommand(__name__)
def net_client(host, port: int):
    ...

Options

To create --option switches, just assign a default. Autocommand will automatically create --long and -short switches.

@autocommand(__name__)
def do_with_config(argument, config='~/foo.conf'):
    pass
$ python example.py -h
usage: example.py [-h] [-c CONFIG] argument

positional arguments:
  argument

optional arguments:
  -h, --help            show this help message and exit
  -c CONFIG, --config CONFIG

The option’s type is automatically deduced from the default, unless one is explicitly given in an annotation:

@autocommand(__name__)
def http_connect(host, port=80):
    print('{}:{}'.format(host, port))
$ python http.py -h
usage: http.py [-h] [-p PORT] host

positional arguments:
  host

optional arguments:
  -h, --help            show this help message and exit
  -p PORT, --port PORT
$ python http.py localhost
localhost:80
$ python http.py localhost -p 8080
localhost:8080
$ python http.py localhost -p blah
usage: http.py [-h] [-p PORT] host
http.py: error: argument -p/--port: invalid int value: 'blah'

None

If an option is given a default value of None, it reads in a value as normal, but supplies None if the option isn’t provided.

Switches

If an argument is given a default value of True or False, or given an explicit bool type, it becomes an option switch.

@autocommand(__name__)
def example(verbose=False, quiet=False):
    pass
$ python example.py -h
usage: example.py [-h] [-v] [-q]

optional arguments:
  -h, --help     show this help message and exit
  -v, --verbose
  -q, --quiet

Autocommand attempts to do the “correct thing” in these cases- if the default is True, then supplying the switch makes the argument False; if the type is bool and the default is some other True value, then supplying the switch makes the argument False, while not supplying the switch makes the argument the default value.

Files

If the default value is a file object, such as sys.stdout, then Autocommand just looks for a string, for a file path. It doesn’t do any special checking on the string, though (such as checking if the file exists); it’s better to let the client decide how to handle errors in this case. Instead, it provides a special context manager called smart_open, which behaves exactly like open if a filename or other openable type is provided, but also lets you use already open files:

from autocommand import autocommand, smart_open
import sys

# Write the contents of stdin, or a file, to stdout
@autocommand(__name__)
def write_out(infile=sys.stdin):
    with smart_open(infile) as f:
        for line in f:
            print(line.rstrip())
    # If a file was opened, it is closed here. If it was just stdin, it is untouched.
$ echo "Hello World!" | python write_out.py | tee hello.txt
Hello World!
$ python write_out.py --infile hello.txt
Hello World!

Descriptions and docstrings

The autocommand decorator accepts description and epilog kwargs, corresponding to the `description <https://docs.python.org/3/library/argparse.html#description>`__ and `epilog <https://docs.python.org/3/library/argparse.html#epilog>`__ of the ArgumentParser. If no description is given, but the decorated function has a docstring, then it is taken as the description for the ArgumentParser

@autocommand(__name__, epilog='Some extra documentation in the epilog')
def copy(infile=sys.stdin, outfile=sys.stdout):
    '''
    Copy an the contents of a file (or stdin) to another file (or stdout)
    '''
    with smart_open(infile) as istr:
        with smart_open(outfile, 'w') as ostr:
            for line in istr:
                ostr.write(line)
$ python copy.py -h
usage: copy.py [-h] [-i INFILE] [-o OUTFILE]

Copy an the contents of a file (or stdin) to another file (or stdout)

optional arguments:
  -h, --help            show this help message and exit
  -i INFILE, --infile INFILE
  -o OUTFILE, --outfile OUTFILE

Some extra documentation in the epilog
$ echo "Hello World" | python copy.py --outfile hello.txt
$ python copy.py --infile hello.txt --outfile hello2.txt
$ python copy.py --infile hello2.txt
Hello World

Parameter descriptions

You can also attach description text to individual parameters in the annotation. To attach both a type and a description, supply them both in any order in a tuple

@autocommand(__name__)
def copy_net(
    infile: 'The name of the file to send',
    host: 'The host to send the file to',
    port: (int, 'The port to connect to')):

    '''
    Copy a file over raw TCP to a remote destination.
    '''
    # Left as an exercise to the reader

Decorators and wrappers

Because autocommand is powered by inspect.signature, it automatically follows wrapper chains created by @functools.wraps. For example:

from functools import wraps
from autocommand import autocommand

def print_yielded(func):
    '''Convert a generator into a function that prints all yielded elements'''
    @wraps(func)
    def wrapper(*args, **kwargs):
        for thing in func(*args, **kwargs):
            print(thing)
    return wrapper

@autocommand(__name__,
    description= 'Print all the values from START to STOP, inclusive, in steps of STEP',
    epilog=      'STOP and STEP default to 1')
@print_yielded
def seq(stop, start=1, step=1):
    for i in range(start, stop + 1, step):
        yield i
$ seq.py -h
usage: seq.py [-h] [-s START] [-S STEP] stop

Print all the values from START to STOP, inclusive, in steps of STEP

positional arguments:
  stop

optional arguments:
  -h, --help            show this help message and exit
  -s START, --start START
  -S STEP, --step STEP

STOP and STEP default to 1

Even though autocommand is being applied to the wrapper returned by print_yielded, it still retreives the signature of the underlying seq function to create the argument parsing.

Testing and Library use

The decorated function is only called and exited from if the first argument to autocommand is '__main__' or True. If it is neither of these values, or no argument is given, then a new main function is created by the decorator. This function has the signature main(*argv), and is intended to be called with arguments as if via main(*sys.argv). Note that this includes the program name, argv[0]. The function has the attributes parser and main, which are the generated ArgumentParser and the original main function that was decorated. This is to facilitate testing and library use of your main. Calling the function triggers a parse_args() with the supplied arguments, and returns the result of the main function. Note that, while it returns instead of calling sys.exit, the parse_args() function will raise a SystemExit in the event of a parsing error or -h/--help argument.

@autocommand()
def test_prog(arg1, arg2: int, quiet=False, verbose=False):
    if not quiet:
        print(arg1, arg2)
        if verbose:
            print("LOUD NOISES")

    return 0

# Note that argv[0] must be included.
print(test_prog('test', '-v', 'hello', '80'))
$ python test_prog.py
hello 80
LOUD NOISES
0

Features, notes, and limitations

  • --options are given single character -short options as well, if possible. Each capitalization of the first letter in the parameter name is tried. If any parameters have only a single letter name, they aren’t given --long versions.

  • autocommand supports a few other kwargs:

    • If a parser is given, that parser object is used instead of one being generated on from the function signature. This allows you to use a more elaborate parser, with features that aren’t supported by the automation system in autocommand.

    • If add_nos is set to True, then for each boolean --switch in the parameter list, a --no-switch is added, to cancel it out.

  • If the decorated function has a *args, then 0 or more arguments are collected into a list. No default value can be given, but a type and/or description annotation may.

  • There are a few possible exceptions that autocommand can raise. All of them derive from autocommand.AutocommandError, which is a TypeError.

    • If an invalid annotation is given (that is, it isn’t a type, str, (type, str), or (str, type), an AnnotationError is raised

    • If the function has a **kwargs parameter, a KWargError is raised.

    • If, somehow, the function has a positional-only parameter, a PositionalArgError is raised. This means that the argument doesn’t have a name, which is currently not possible with a plain def or lambda, though many built-in functions have this kind of parameter.

  • There are a few argparse features that are not supported by autocommand.

    • It isn’t possible to have an optional positional argument (as opposed to a --option). POSIX and GNU think this is bad form anyway.

    • It isn’t possible to have mutually exclusive arguments or options

    • It isn’t possible to have subcommands or subparsers, though I’m working on a few solutions involving classes or nested function definitions to allow this.

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

autocommand-0.9.5.tar.gz (13.5 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

autocommand-0.9.5-py3-none-any.whl (14.2 kB view details)

Uploaded Python 3

File details

Details for the file autocommand-0.9.5.tar.gz.

File metadata

  • Download URL: autocommand-0.9.5.tar.gz
  • Upload date:
  • Size: 13.5 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No

File hashes

Hashes for autocommand-0.9.5.tar.gz
Algorithm Hash digest
SHA256 49080c8e18e90ffe209ed100540fd88be065b7826f1410c382ad45f4f9defc7c
MD5 2e9f68349bee85752a8961de49becf43
BLAKE2b-256 0c14ab155d19f7be7aee1af791c4e63dbdc43cd1695c96ae17a38d604b1d6457

See more details on using hashes here.

File details

Details for the file autocommand-0.9.5-py3-none-any.whl.

File metadata

File hashes

Hashes for autocommand-0.9.5-py3-none-any.whl
Algorithm Hash digest
SHA256 c80d1b17192b97eb9e397c39ee23399b2321a5d97fce2ce3093ad720b6c1fb6b
MD5 87284c76e6f90fa3105bd5e77270a457
BLAKE2b-256 1cdbe84afc9e0f42ace173a10fb33aad852f3bb13f807cc137a95dd26888f954

See more details on using hashes here.

Release history Release notifications | RSS feed

2.2.2

2 files

2.2.1

2 files

2.2.0

2 files

2.1.5

2 files

2.1.4

2 files

2.1.3

2 files

2.1.2

2 files

2.1.1

2 files

2.1.0

2 files

2.0.1

2 files

2.0.0

2 files

1.0.2

2 files

1.0.1

2 files

1.0.0

2 files

0.9.6

2 files

This release

0.9.5 This release

2 files

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