Rich-argparse

Latest version: v1.7.0

Safety actively analyzes 723158 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 2 of 4

1.3.0

Features
- [PR-87](https://github.com/hamdanal/rich-argparse/pull/87)
Add `optparse.GENERATE_USAGE` to auto generate a usage similar to argparse.
- [PR-87](https://github.com/hamdanal/rich-argparse/pull/87)
Add `rich_format_*` methods to optparse formatters. These return a `rich.text.Text` object.

Fixes
- [GH-79](https://github.com/hamdanal/rich-argparse/issues/79),
[PR-80](https://github.com/hamdanal/rich-argparse/pull/80),
[PR-85](https://github.com/hamdanal/rich-argparse/pull/85)
Fix ansi escape codes on legacy Windows console

1.2.0

Features
- [PR-73](https://github.com/hamdanal/rich-argparse/pull/73)
Add experimental support for `optparse`. Import optparse formatters from `rich_argparse.optparse`.

Changes
- [PR-72](https://github.com/hamdanal/rich-argparse/pull/72)
The project now uses `ruff` for linting and import sorting.
- [PR-71](https://github.com/hamdanal/rich-argparse/pull/71)
`rich_argparse` is now a package instead of a module. This should not affect users.

Fixes
- [PR-74](https://github.com/hamdanal/rich-argparse/pull/74)
Fix crash when a metavar following a long option contains control codes.

1.1.1

Fixes
- [GH-67](https://github.com/hamdanal/rich-argparse/issues/67),
[PR-69](https://github.com/hamdanal/rich-argparse/pull/69)
Fix `%` not being escaped properly
- [PR-68](https://github.com/hamdanal/rich-argparse/pull/68)
Restore lazy loading of `rich`. Delay its import until it is needed.

1.1.0

Features
- [GH-55](https://github.com/hamdanal/rich-argparse/issues/55),
[PR-56](https://github.com/hamdanal/rich-argparse/pull/56)
Add a new style for `%(prog)s` in the usage. The style is applied in argparse-generated usage and
in user defined usage whether the user usage is plain text or rich markup.

1.0.0

Fixes
- [GH-49](https://github.com/hamdanal/rich-argparse/issues/49),
[PR-50](https://github.com/hamdanal/rich-argparse/pull/50)
`RichHelpFormatter` now respects format conversion types in help strings

0.7.0

Features
- [GH-47](https://github.com/hamdanal/rich-argparse/issues/47),
[PR-48](https://github.com/hamdanal/rich-argparse/pull/48)
The default `group_name_formatter` has changed from `str.upper` to `str.title`. This renders
better with long group names and follows the convention of popular CLI tools and programs.
Please note that if you test the output of your CLI **verbatim** and rely on the default behavior
of rich_argparse, you will have to either set the formatter explicitly or update the tests.

Page 2 of 4

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.