From 606de27656503edeebae537a9e535925856b9f7c Mon Sep 17 00:00:00 2001 From: Iain Date: Sat, 31 Oct 2026 18:28:19 +0000 Subject: [PATCH] docs: drop Python Fire from the CLI Development intro --- website/data/category_intros/cli-development.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/website/data/category_intros/cli-development.md b/website/data/category_intros/cli-development.md index 9c2009bcf6..5d819b009f 100644 --- a/website/data/category_intros/cli-development.md +++ b/website/data/category_intros/cli-development.md @@ -6,7 +6,6 @@ How to choose: - Nested commands, or subcommands loaded lazily: Click - Options declared once as type-hinted function parameters: Typer - Interactive prompts and REPLs: prompt_toolkit -- CLI from existing code without writing a parser: Python Fire - Progress bar for a loop: tqdm, or alive-progress for animated bars - Colored text, tables, and logs: Rich, or colorama for ANSI colors on Windows - Full-screen app in the terminal or a browser: Textual @@ -21,8 +20,6 @@ Typer builds a CLI from your function signatures: you [declare each argument and prompt_toolkit is for interactive input. It can [replace GNU readline](https://python-prompt-toolkit.readthedocs.io/en/stable/) or build full-screen apps. For a REPL, use a [`PromptSession`](https://python-prompt-toolkit.readthedocs.io/en/stable/pages/asking_for_input.html), which keeps the history for the whole session. -Python Fire turns any Python object into a CLI: [call `fire.Fire()`](https://github.com/google/python-fire/blob/master/docs/guide.md) at the end of your program. Its README pitches it for [developing and debugging your code](https://github.com/google/python-fire), exploring existing code, and turning other people's code into a CLI. It takes each argument's type from the value you pass, not from the function signature. - tqdm adds a progress bar to any loop: [wrap the iterable in `tqdm()`](https://github.com/tqdm/tqdm). Import it from `tqdm.auto`, which picks the console bar or the Jupyter widget for you. alive-progress wraps the loop in an [`alive_bar` context manager](https://github.com/rsalmei/alive-progress) instead, with a spinner that speeds up and slows down with your throughput. Rich writes colored text, tables, Markdown, and syntax-highlighted code to the terminal. Start with its [drop-in `print`](https://rich.readthedocs.io/en/stable/introduction.html), then create [one `Console` at module level](https://rich.readthedocs.io/en/stable/console.html) for the rest of your app. For colored logs, send the logging module's output through [`RichHandler`](https://rich.readthedocs.io/en/stable/logging.html).