Skip to content

chore(deps): update dependency fire to v0.7.1 #13

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
renovate wants to merge 1 commit into
base: master
Choose a base branch
from
Open

chore(deps): update dependency fire to v0.7.1 #13

renovate wants to merge 1 commit into from

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Oct 31, 2025 •
edited
Loading

This PR contains the following updates:

Package Change Age Confidence
fire ==0.1.3 → ==0.7.1 age confidence

Release Notes

google/python-fire (fire)

v0.7.1: Python Fire v0.7.1

Compare Source

What's Changed

  • Use Neutral theme for IPython Inspector, supporting newer IPython versions in #​588
  • Call inspectutils.GetClassAttrsDict on component, not None in #​606
  • Move to pyproject.toml, adding wheel support in pypi
  • Use ty in place of pytype
  • Update requirements @​dependabot[bot]

Full Changelog: google/python-fire@v0.7.0...v0.7.1

v0.7.0: Python Fire v0.7.0

Compare Source

Notable in this release:

  • This release is the first to drop Python 2 support. For Python 2 users, use <= 0.6.0.
  • CI improvements from @​Borda including dependabot and an expanded build matrix

What's Changed

New Contributors

Full Changelog: google/python-fire@v0.6.0...v0.7.0

v0.6.0: Python Fire v0.6.0

Compare Source

This is the last release supporting Python 2. Subsequent releases will be Python 3 only. The automatically generated release notes follow.

What's Changed
New Contributors

Full Changelog: google/python-fire@v0.5.0...v0.6.0

v0.5.0: Python Fire v0.5.0

Compare Source

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.

v0.4.0: Python Fire v0.4.0

Compare Source

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.

v0.3.1

Compare Source

Removes preexec_fn from pager subprocess call. Resolves #​236.

v0.3.0

Compare Source

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 f01aad3
  • 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

v0.2.1

Compare Source

Bug fixes

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

v0.2.0

Compare Source

Python Fire v0.2.0

If you're new to Python Fire:

  1. Welcome! 🎉
  2. 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

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/fire-0.x branch from d8d0201 to 3d4d98b Compare November 11, 2025 01:36
@renovate renovate bot force-pushed the renovate/fire-0.x branch from 3d4d98b to 58bdd5f Compare December 3, 2025 14:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants