Rewriting an argparse-based CLI with #Cappa. It's much cleaner:

- less verbose
- better contained (single module instead of using submodules for subcommands)
- better typed (dataclasses!)
- as reusable, or more reusable in other CLIs (classes instead of functions that modify an argparse parser)
- much easier to use programmatically (no need to call `main` or build an `argparse.Namespace` manually)
- better documented
- better output (rich!)

https://github.com/DanCardin/cappa

#Cappa is awesome. @dancardin does a fantastic job on this project.

Command descriptions can be written in Markdown and are rendered with #Rich, so code blocks are syntax highlighted, and you can even add links. Amazing CLI experience.

Look at this beauty:

What a rabbit hole. Even though #Cappa uses #Rich internally, forcing colors with `FORCE_COLOR=1` did not work.

After a super painful investigation, turns out my #Python code imports a module from #Copier which uses `colorama.init()`.

Changing that to `colorama.just_fix_windows_console()` fixed it, but the output still had an extra reset sequence at the end.

Turns out Copier imports #Plumbum colors module, which registers a function to reset styles at exit.

Don't run things at import time!

#Cappa puts the finger on what I dislike about #Click: https://cappa.readthedocs.io/en/latest/comparison.html#why-not-click. I'll try Cappa right now in a new project.

I was also strongly tempted by #arguably (https://github.com/treykeown/arguably), but Cappa's use of `Annotated` instead of docstrings makes it super attractive given my recent work on supporting PEP 727 (from @tiangolo) with a #Griffe extension.