Python Fire is a library for automatically generating command line interfaces (CLIs) from absolutely any Python object.

Last update: Dec 31, 2022

Overview

Python Fire

Python Fire is a library for automatically generating command line interfaces (CLIs) from absolutely any Python object.

Python Fire is a simple way to create a CLI in Python. [1]
Python Fire is a helpful tool for developing and debugging Python code. [2]
Python Fire helps with exploring existing code or turning other people's code into a CLI. [3]
Python Fire makes transitioning between Bash and Python easier. [4]
Python Fire makes using a Python REPL easier by setting up the REPL with the modules and variables you'll need already imported and created. [5]

Installation

To install Python Fire with pip, run: pip install fire

To install Python Fire with conda, run: conda install fire -c conda-forge

To install Python Fire from source, first clone the repository and then run: python setup.py install

Basic Usage

You can call Fire on any Python object:
functions, classes, modules, objects, dictionaries, lists, tuples, etc. They all work!

Here's an example of calling Fire on a function.

import fire

def hello(name="World"):
  return "Hello %s!" % name

if __name__ == '__main__':
  fire.Fire(hello)

Then, from the command line, you can run:

python hello.py  # Hello World!
python hello.py --name=David  # Hello David!
python hello.py --help  # Shows usage information.

Here's an example of calling Fire on a class.

import fire

class Calculator(object):
  """A simple calculator class."""

  def double(self, number):
    return 2 * number

if __name__ == '__main__':
  fire.Fire(Calculator)

Then, from the command line, you can run:

python calculator.py double 10  # 20
python calculator.py double --number=15  # 30

To learn how Fire behaves on functions, objects, dicts, lists, etc, and to learn about Fire's other features, see the Using a Fire CLI page.

For additional examples, see The Python Fire Guide.

Why is it called Fire?

When you call Fire, it fires off (executes) your command.

Where can I learn more?

Please see The Python Fire Guide.

Reference

Setup	Command	Notes
install	`pip install fire`

Creating a CLI	Command	Notes
import	`import fire`
Call	`fire.Fire()`	Turns the current module into a Fire CLI.
Call	`fire.Fire(component)`	Turns `component` into a Fire CLI.

Using a CLI	Command	Notes
Help	`command --help` or `command -- --help`
REPL	`command -- --interactive`	Enters interactive mode.
Separator	`command -- --separator=X`	Sets the separator to `X`. The default separator is `-`.
Completion	`command -- --completion [shell]`	Generates a completion script for the CLI.
Trace	`command -- --trace`	Gets a Fire trace for the command.
Verbose	`command -- --verbose`

Note that these flags are separated from the Fire command by an isolated --.

License

Licensed under the Apache 2.0 License.

Disclaimer

This is not an official Google product.

Comments

incorrect control code displayed in Windows console.

when I run the basic example code. there are some control code displayed as output text. I guess it probably some color effects?

How do I avoid it?

[1mFLAGS[0m --minputs=[4mMINPUTS[0m --moutputs=[4mMOUTPUTS[0m

[1mNOTES[0m You can also use flags syntax for POSITIONAL ARGUMENTS
bug help wanted

opened by wenbingl 27
Use fire without editing code directly
Currently you have to add something like this to the end of your file just to mess around with fire:

if __name__ == '__main__': fire.Fire()

and then run with

python path/to/code.py

But it'd be neat if instead you could just do

fire path/to/code.py

and that does equivalent of exec appending the ifmain statement to the end.

Not sure how to do it - I know kernprof does some magic to inject into builtins before exec'ing code. (or maybe you get a code object back from exit) - but this would make fire even better as a debugging tool as well.
opened by jtratner 27

use --help or -h to show comment info

Is there any way that can use "-h" or "--help" to show comment of a function or class.

example:

#!/usr/bin/env python
# -*- coding: utf-8 -*-
"""
:authors: wanglichao
:version: 1.0 of 2017-03-20

"""

import fire


def hello(name):
    """this is a hello test1
    """
    return 'Hello {name}!'.format(name=name)


def hello2(name):
    """this is a hello test2
    """
    return 'Hello {name}!'.format(name=name)


if __name__ == '__main__':
    fire.Fire()

expect result:

python hello.py -- --help

Usage: hello.py [OPTIONS] COMMAND [ARGS]...
             authors: wanglichao
             version: 1.0 of 2017-03-20

Options:
             -- --help
             -- --interactive
             -- --trace
             -- --verbose

Command:
             fire           inner command
             hello          this is a hello test1
             hello2         this is a hello test2

opened by xidianwlc 21

Issue #108: Shortcuts for boolean arguments
In response to this issue. This adds a feature where a shortcut can be used for boolean arguments of functions. For example the function

def foo(bar=False):

can be invoked as foo -b to set bar to True. While developing this, I came across a couple concerns:

In detecting whether or not arguments matched the pattern of a bool shortcut, I decided that python's regex library was the best way to solve this problem. Is adding re to imports ok?

If a naming collision occurs (see final assert of testBoolShortcutParsing) the program raises a FireError describing the ambiguity. Is this a proper manner to use this error in?

Currently, if a shortcut doesn't match any function argument, it is parsed as-is. Should something else be done in this scenario?
opened by alexshadley 17

Add custom formatter for Fire result

Fixes #344 (see issue for more details)

This lets you define a function that will take the result from the Fire component and allows the user to alter it before fire looks at it to render it.

Why? Because you want to define a global way of formatting your data for your CLI across a family of functions/classes where it is impractical (and a major pain) to wrap them all.

Outputting tabular data:

import random
def data():
    return [
        {
            'is_up': random.choice([False, True]), 
            'value_A': random.random(), 
            'value_B': random.random() + 100,
            'id': random.randint(1000, 5000)} 
        for i in range(8)
    ]

import fire
fire.Fire(data)

Outputs this:

{"is_up": true, "value_A": 0.6004291859538904, "value_B": 100.77910907893889, "id": 474}
{"is_up": false, "value_A": 0.1406617230697117, "value_B": 100.35721554966845, "id": 740}
{"is_up": true, "value_A": 0.3612392830626744, "value_B": 100.60814663568802, "id": 509}
{"is_up": false, "value_A": 0.11247653550250092, "value_B": 100.2673181440675, "id": 305}
{"is_up": false, "value_A": 0.9505598630828166, "value_B": 100.84615141986525, "id": 85}
{"is_up": true, "value_A": 0.17544933002396768, "value_B": 100.66062056951291, "id": 385}
{"is_up": false, "value_A": 0.25245927587860695, "value_B": 100.75492369068093, "id": 923}
{"is_up": true, "value_A": 0.9237200249249168, "value_B": 100.94228120845642, "id": 702}

But if we can define a formatter.

import tabulate

def fancy_table(result):
    if not result:  # show a message instead of an empty response
        return 'nada. sorry.'
    
    # display a list of dicts as a table
    if isinstance(result, (list, tuple)) and all(isinstance(x, dict) for x in result):
        return tabulate.tabulate([
            {col: cell_format(value) for col, value in row.items()}
            for row in result
        ], headers="keys")

    return result  # otherwise, let fire handle it

def cell_format(value, decimals=3, bool=('🌹', '🥀')):
    if value is True:
        return bool[0]
    if value is False:
        return bool[1]
    if isinstance(value, float):
        return '{:.{}f}'.format(value, decimals)
    return value

fire.Fire(data, formatter=fancy_table)

Outputs this:

is_up      value_A    value_B    id
-------  ---------  ---------  ----
🌹           0.115    100.013  1821
🌹           0.439    100.167  4242
🥀           0.68     100.345  2937
🥀           0.074    100.119  4675
🌹           0.189    100.462  4571
🌹           0.221    100.342  1522
🌹           0.02     100.452  2363
🥀           0.023    100.812  2433

Using a formatter means that:

if you don't provide a formatter, or if your formatter returns the original value (lambda x: x) then nothing is changed
if you want to change how some value is displayed, you can just return what you want it to render as e.g. lambda x: {'idk why, but': x} if isinstance(x, list) else x
if you are unable to make a class __str__ representation look like you want it to, you can handle it in the formatter instead e.g. lambda x: custom_str(x) if isinstance(x, some_class) else x
if you want to display nested dictionaries as yaml, you can use yaml.dump as a formatter
you can suppress output e.g. lambda x: None
you can handle printing yourself by printing inside the formatter and returning None to suppress fire formatting

cla: yes

opened by beasteers 15

Fix several warnings in the diff example

Fixes ResourceWarning unclosed file:

examples/diff/diff.py:78: ResourceWarning: unclosed file <_io.TextIOWrapper name='/tmp/tmpnby8pemm' mode='U' encoding='UTF-8'>
    self.tolines = open(tofile, 'U').readlines()

And DeprecationWarning 'U' mode is deprecated:

examples/diff/diff_test.py::DiffTest::testUnifiedDiff
  examples/diff/diff.py:77: DeprecationWarning: 'U' mode is deprecated
    with open(fromfile, 'U') as f:

opened by BoboTiG 14

Multi-line parameter descriptions in Google-style docstrings

Hey there! Quick question regarding the behavior of multi-line parameter descriptions in Google-style docstrings.

Consider the following code:

# main.py
def foo(bar):
    """
    This does a foo on a bar.

    Args:
        bar (str): Though a simple parameter, this parameter will need a lot of
            verbiage to describe, requiring a second line.
    """
    print(f"Hi, {bar}!")

if __name__ == "__main__":
    import fire

    fire.Fire(foo)

When running main.py --help, the resulting man is:

NAME
    main.py - This does a foo on a bar.

SYNOPSIS
    main.py BAR

DESCRIPTION
    This does a foo on a bar.

POSITIONAL ARGUMENTS
    BAR
        Though a simple parameter, this parameter will need a lot of

NOTES
    You can also use flags syntax for POSITIONAL ARGUMENTS

Notice that we are losing the following line here.

I'd expect the newline-containing description to be un-newlined (definitely not a word)

NAME
    main.py - This does a foo on a bar.

SYNOPSIS
    main.py BAR

DESCRIPTION
    This does a foo on a bar.

POSITIONAL ARGUMENTS
    BAR
        Though a simple parameter, this parameter will need a lot of verbiage to describe, requiring a second line.

NOTES
    You can also use flags syntax for POSITIONAL ARGUMENTS

Or maybe included with the newline, but in some way retaining the following line. Any plans to support this, or (likely) am I missing something?

bug help wanted

opened by lukedeo 12

fire.py: Use fire on arbitrary file or module.

Based on the discussion at Use fire without editing code directly · Issue #29 · google/python-fire

Of course, still needs better error handling, documentation, installation support, etc.

opened by nealmcb 12
Remove `IPython` dependency from `fire.Fire` or improve load times some other way

import IPython takes about 0.5 seconds on my machine to import and is the longest part of running simple fire scripts at the moment. Launching a python script and printing something takes 0.15 seconds so the total with import fire becomes about 0.65 seconds.

It's only used in _EmbedIPython and inspectutils.py so maybe it can be optional for command line apps and the inspection part ported over (or placed in a different smaller package)? Would such a pull request be useful?
enhancement

opened by ubershmekel 12

example in docs for grouping has no output

Hello, following the docs here: https://github.com/google/python-fire/blob/master/docs/guide.md#grouping-commands

I am unable to get this to run when calling

example.py run

It currently returns no output.

If I run either of the digestion run or ingestion run commands they work flawlessly just not the grouped command

Heres the code:

import fire

class IngestionStage(object):

  def run(self):
    return 'Ingesting! Nom nom nom...'

class DigestionStage(object):

  def run(self, volume=1):
    return ' '.join(['Burp!'] * volume)

  def status(self):
    return 'Satiated.'

class Pipeline(object):

  def __init__(self):
    self.ingestion = IngestionStage()
    self.digestion = DigestionStage()

  def run(self):
    self.ingestion.run()
    self.digestion.run()

if __name__ == '__main__':
  fire.Fire(Pipeline)

documentation

opened by MSAdministrator 11

How can I use default arguments in a method with python-fire? Possible bug. Feature request: Argument in `fire.Fire` to force using keyword args
I am having an issue with python-fire when a method has arguments with default values. Consider the following code:

import fire class SomeClass(object): def __init__(self): self.a = '' self.b = '' def methoda(self): self.a = 'A' return self def methodb(self, x='B123'): self.b = self.a + x return self def __str__(self): return self.b if __name__ == '__main__': s = SomeClass() s.methodb().methoda() print(s.b) # this prints B123 correctly fire.Fire(SomeClass)

As seen in the comments, in the print(s.b), it is printingB123` correctly. But when i change the order of the methods being called in fire from the command line, I am getting the odd behavior.

Example:

> python x.py B123 # correct > python x.py methoda methodb Here: B123 AB123 # both correct > python x.py methodb --x B123 methoda Here: B123 B123 # again both correct > python x.py methodb methoda Here: B123 methoda # this is not correct. It should print B123 here also

As you can see with the last example, if i call methodb (which has an argument with a default value), it prints methoda instead of B123 as expected.

My question is, How can I use a method that has a default argument value first in this type of scenario without passing in --x=something?

In short, how can i make > python x.py methodb methoda properly print B123? Second question is, how can I show the method args in the help? Currently it shows nothing when there is a default value assigned. When I do methoda methodb, I do not have to pass --x=B123, but if I move the method with the default argument value up, it doesnt work as seen in the example.
opened by securisec 11

Fails build on python3.11?

Hi, I noticed the #1026619 that was marked removal for python-fire package on Debian. The problem is that it build fails on here：

I: pybuild base:240: cd /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build; python3.11 -m unittest discover -v
fire.test_components (unittest.loader._FailedTest.fire.test_components) ... ERROR
fire.test_components_bin (unittest.loader._FailedTest.fire.test_components_bin) ... ERROR
fire.test_components_py3 (unittest.loader._FailedTest.fire.test_components_py3) ... ERROR
fire.test_components_test (unittest.loader._FailedTest.fire.test_components_test) ... ERROR
....
======================================================================
ERROR: fire.test_components (unittest.loader._FailedTest.fire.test_components)
----------------------------------------------------------------------
ImportError: Failed to import test module: fire.test_components
Traceback (most recent call last):
  File "/usr/lib/python3.11/unittest/loader.py", line 407, in _find_test_path
    module = self._get_module_from_name(name)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/unittest/loader.py", line 350, in _get_module_from_name
    __import__(name)
  File "/<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/fire/test_components.py", line 28, in <module>
    from fire import test_components_py3 as py3  # pylint: disable=unused-import,no-name-in-module,g-import-not-at-top
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/fire/test_components_py3.py", line 58, in <module>
    class WithAsyncio(object):
  File "/<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/fire/test_components_py3.py", line 60, in WithAsyncio
    @asyncio.coroutine
     ^^^^^^^^^^^^^^^^^
AttributeError: module 'asyncio' has no attribute 'coroutine'


======================================================================
ERROR: fire.test_components_bin (unittest.loader._FailedTest.fire.test_components_bin)
----------------------------------------------------------------------
ImportError: Failed to import test module: fire.test_components_bin
Traceback (most recent call last):
  File "/usr/lib/python3.11/unittest/loader.py", line 407, in _find_test_path
    module = self._get_module_from_name(name)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/unittest/loader.py", line 350, in _get_module_from_name
    __import__(name)
  File "/<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/fire/test_components_bin.py", line 25, in <module>
    from fire import test_components
  File "/<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/fire/test_components.py", line 28, in <module>
    from fire import test_components_py3 as py3  # pylint: disable=unused-import,no-name-in-module,g-import-not-at-top
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/fire/test_components_py3.py", line 58, in <module>
    class WithAsyncio(object):
  File "/<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/fire/test_components_py3.py", line 60, in WithAsyncio
    @asyncio.coroutine
     ^^^^^^^^^^^^^^^^^
AttributeError: module 'asyncio' has no attribute 'coroutine'


======================================================================
ERROR: fire.test_components_py3 (unittest.loader._FailedTest.fire.test_components_py3)
----------------------------------------------------------------------
ImportError: Failed to import test module: fire.test_components_py3
Traceback (most recent call last):
  File "/usr/lib/python3.11/unittest/loader.py", line 407, in _find_test_path
    module = self._get_module_from_name(name)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/unittest/loader.py", line 350, in _get_module_from_name
    __import__(name)
  File "/<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/fire/test_components_py3.py", line 58, in <module>
    class WithAsyncio(object):
  File "/<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/fire/test_components_py3.py", line 60, in WithAsyncio
    @asyncio.coroutine
     ^^^^^^^^^^^^^^^^^
AttributeError: module 'asyncio' has no attribute 'coroutine'


======================================================================
ERROR: fire.test_components_test (unittest.loader._FailedTest.fire.test_components_test)
----------------------------------------------------------------------
ImportError: Failed to import test module: fire.test_components_test
Traceback (most recent call last):
  File "/usr/lib/python3.11/unittest/loader.py", line 407, in _find_test_path
    module = self._get_module_from_name(name)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/unittest/loader.py", line 350, in _get_module_from_name
    __import__(name)
  File "/<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/fire/test_components_test.py", line 21, in <module>
    from fire import test_components as tc
  File "/<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/fire/test_components.py", line 28, in <module>
    from fire import test_components_py3 as py3  # pylint: disable=unused-import,no-name-in-module,g-import-not-at-top
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/fire/test_components_py3.py", line 58, in <module>
    class WithAsyncio(object):
  File "/<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/fire/test_components_py3.py", line 60, in WithAsyncio
    @asyncio.coroutine
     ^^^^^^^^^^^^^^^^^
AttributeError: module 'asyncio' has no attribute 'coroutine'


----------------------------------------------------------------------
Ran 7 tests in 0.001s

I have googled the asyncio was Deprecated here, right? Could you have a look?

Thanks.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026619

opened by yuzibo 1

Support case-insensitive usage

Refers to #43

Sample usage:

import fire

class Example(object):
  def alpha(self):
    return 'alpha'
  def Alpha(self):
    return 'Alpha'
  def Beta(self):
    return 'Beta'

if __name__=='__main__':
	fire.Fire(Example)

$ python test.py alpha
alpha

$ python test.py Alpha
Alpha

$ python test.py beta
Beta

$ python test.py BETA
NOTE: Consider using the correct capitalization for BETA
ERROR: Ambiguous member access: BETA
Usage: test.py <command>
  available commands:    Alpha | Beta | alpha

For detailed information on this command, run:
  test.py --help

opened by meowmeowmeowcat 0

Update in setup.cfg: license-file -> license_files

This happens both in version 0.5.0 and in master:

 * QA Notice: setuptools warnings detected:
 * 
 * 	The license_file parameter is deprecated, use license_files instead.
 * 	Usage of dash-separated 'license-file' will not be supported in future versions. Please use the underscore name 'license_file' instead

opened by martenwa 1

Tests are installed

Hi! I package this project for Arch Linux.

I noticed, that all test files are installed when installing this package. Although the test files should be part of an sdist or source tarball, they should not be installed to the target system, as tests should be run beforehand.

Moving the various *_test.py and testutils.py files from the fire/ directory to a dedicated tests/ directory would help you to ignore them for installation.

opened by dvzrv 1

Releases(v0.5.0)

v0.5.0(Dec 12, 2022)
Changelist

Support for custom serializers with fire.Fire(serializer=your_serializer) #345

Auto-generated help text now shows short arguments (e.g. -a) when appropriate #318

Documentation improvements (#334, #399, #372, #383, #387)

Default values are now shown in help for kwonly arguments #414

Completion script fix where previously completions might not show at all #336

Highlighted change: fire.Fire(serialize=custom_serialize_fn) #345

You can now pass a custom serialization function to fire to control how the output is serialized.

Your serialize function should accept an object as input, and may return a string as output. If it returns a string, Fire will display that string. If it returns None, Fire will display nothing. If it returns something else, Fire will use the default serialization method to convert it to text.

The default serialization remains unchanged from previous versions. Primitives and collections of primitives are serialized one item per line. Objects that define a custom __str__ function are serialized using that. Complex objects that don't define __str__ trigger their help screen rather than being serialized and displayed.
Source code(tar.gz)
Source code(zip)
v0.4.0(Jan 22, 2021)
Changelist

Support for Python 3.8 and Python 3.9

Argument types and defaults appear in help text

Support for asyncio coroutines

Support for modules and Python files with python -m fire

Keyword argument info from rst docstrings appears in help text

Bug fix for missing parts of multiline argument descriptions from Google and Numpy style docstrings.

Packaging of enum34

Support functions even when they override getattr in non-standard ways. (e.g. supports BeautifulSoup)

Highlighted change: python -m fire

You can use Python Fire without ever modifying your code. To use it, first install Python Fire with pip install fire. Then simply run python -m fire path/to/yourfile.py or python -m fire path.to.yourmodule.

This is both a fast way to use Python Fire to create a CLI from your code, and a way to apply Python Fire quickly to a codebase you don't have access to.
Source code(tar.gz)
Source code(zip)
v0.3.1(Apr 7, 2020)

Removes preexec_fn from pager subprocess call. Resolves #236.
Source code(tar.gz)
Source code(zip)
v0.3.0(Mar 24, 2020)
Assorted Improvements in Python Fire v0.3.0

Use Fire on third-party code without making any code changes: python -m fire <module>

Docstring parsing fix for all lines are blank f01aad347632791e3438c1a753e42a514520d690

Improved parsing of numpy-style docstrings

#187 Expose built-in functions from the standard library (e.g. sin, cos)

#149 Support objects implementing __getattr__

#205 Fix ctrl-C handling in help screens

Support functools.wraps and lru_cache decorated functions

Better support for objects with properties

Objects with custom __str__ are now treated as Values. E.g. If such an object appears in a dict, the dict will still print in line-by-line mode rather than showing a help screen by default.

Formatting on Windows works properly now

Source code(tar.gz)
Source code(zip)
v0.2.1(Aug 1, 2019)
Bug fixes

Improves robustness of docstring parser in the face of unexpected format docstrings. #183

Source code(tar.gz)
Source code(zip)
v0.2.0(Jul 26, 2019)
Python Fire v0.2.0

If you're new to Python Fire:

Welcome! 🎉

Fire automatically generates command line interfaces from any Python object you give it. 🔥

e.g. You can call Fire on a function, as in this example (but you can also call Fire on anything else: classes, objects, dicts, etc. -- they all work.)

def hello(name="World"): return "Hello %s!" % name fire.Fire(hello)

hello.py --name=David # Hello David!

pip install fire to get started.

Improvements in v0.2.0

Help and usage screens Help screens now have a man-page appearance and are shown with less-style pagination. Usage screens are shown when a user-error is encountered. The help and usage screens are considerably cleaner than the default output in previous versions of Fire.

Custom serialization If you define a custom __str__ method on an object, that will be used to serialize the object when it is the final result of a Fire command. This means better support for numpy arrays, and better support for custom types.

Docstring parsing Notably, docstrings are parsed in order to determine the descriptions to use for arguments in the help screens. We largely support (but not fully) Google, numpy, and RST style docstrings. These are the three most common styles of docstring used in Python code.

Access --help naturally You no longer need to separate --help from your command with an extra --. Simply running command -h or command --help will give help, provided there isn't an argument named help in your component.

NamedTuples can be indexed both by their field names and by their indexes.

Callable objects can both be called, and their members can be accessed. You must use flag syntax to call a callable object; you cannot pass their arguments positionally.

Single-hyphen flags are supported You can now specify -flag instead of --flag if preferred. Both work.

Short-flags are permitted when their use is unambiguous E.g. if your function has argument alpha, then you can specify its value with -a.

Fish completion support

Source code(tar.gz)
Source code(zip)
v0.1.3(Feb 23, 2018)
This release has a few small improvements:

Do not treat arguments that start with '--' as strings [#99]

Fix for BinOps in args [#96]

six.u for Python 3 compatability in fuzz tests [#111]

And a small packaging improvement:

Files in PyPi archive are world readable. [#107]

Source code(tar.gz)
Source code(zip)
v0.1.2(Aug 29, 2017)
Improvements

IPython is fully optional! [#7] Now Fire's only dependency is six (the Python 2, 3 compatibility module) which is fairly light weight. If you use Fire without IPython, we call it "Fire Lite." Pun intended.

The command argument accepts lists [#53] fire.Fire's optional command argument now accepts either a sequence of arguments or a single string. Previously the command argument only accepted a string.

New mkdocs documentation We've started using mkdocs for documentation. The documentation is available at https://google.github.io/python-fire.

Packaging improvements: the license file is now included in the release.

Output is no longer force converted to ASCII.

Source code(tar.gz)
Source code(zip)
v0.1.1(May 21, 2017)
New Features

The Python Fire Guide is available

Support for annotations in functions

Support for keyword-only arguments in functions

Faster loading via lazy imports

Bug Fixes

Serialize empty dictionaries

Serialize dictionaries with circular dependencies

Support non-comparable objects, numpy arrays, etc

Help for objects without source files

Completion scripts for top-level functions

Source code(tar.gz)
Source code(zip)

Owner

Google

Google ❤️ Open Source

GitHub Repository

Python library to build pretty command line user prompts ✨Easy to use multi-select lists, confirmations, free text prompts ...

Questionary ✨ Questionary is a Python library for effortlessly building pretty command line interfaces ✨ Features Installation Usage Documentation Sup

990 Jan 01, 2023

A cross platform package to do curses-like operations, plus higher level APIs and widgets to create text UIs and ASCII art animations

ASCIIMATICS Asciimatics is a package to help people create full-screen text UIs (from interactive forms to ASCII animations) on any platform. It is li

3.2k Jan 09, 2023

Python Fire is a library for automatically generating command line interfaces (CLIs) from absolutely any Python object.

Related tags

Overview

Python Fire

Installation

Basic Usage

Why is it called Fire?

Where can I learn more?

Reference

License

Disclaimer

Comments

Outputting tabular data:

Releases(v0.5.0)

v0.5.0(Dec 12, 2022)

Changelist

Highlighted change: fire.Fire(serialize=custom_serialize_fn) #345

v0.4.0(Jan 22, 2021)

Changelist

Highlighted change: python -m fire

v0.3.1(Apr 7, 2020)

v0.3.0(Mar 24, 2020)

Assorted Improvements in Python Fire v0.3.0

v0.2.1(Aug 1, 2019)

v0.2.0(Jul 26, 2019)

Python Fire v0.2.0

Improvements in v0.2.0

v0.1.3(Feb 23, 2018)

v0.1.2(Aug 29, 2017)

v0.1.1(May 21, 2017)

Owner

Google

Python library to build pretty command line user prompts ✨Easy to use multi-select lists, confirmations, free text prompts ...

A cross platform package to do curses-like operations, plus higher level APIs and widgets to create text UIs and ASCII art animations

Pythonic command line arguments parser, that will make you smile

Typer, build great CLIs. Easy to code. Based on Python type hints.

Terminalcmd - a Python library which can help you to make your own terminal program with high-intellegence instruments

A fast, stateless http slash commands framework for scale. Built by the Crunchy bot team.

A thin, practical wrapper around terminal capabilities in Python

plotting in the terminal

A CLI tool to build beautiful command-line interfaces with type validation.

Library for building powerful interactive command line applications in Python

Command line animations based on the state of the system

Python library that measures the width of unicode strings rendered to a terminal

A module for parsing and processing commands.

Python Command-line Application Tools

Python Fire is a library for automatically generating command line interfaces (CLIs) from absolutely any Python object.

sane is a command runner made simple.

Python composable command line interface toolkit

emoji terminal output for Python

A minimal and ridiculously good looking command-line-interface toolkit

A simple terminal Christmas tree made with Python

Highlighted change: `fire.Fire(serialize=custom_serialize_fn)` #345

Highlighted change: `python -m fire`