rich-python

Inject a Console configured with file=StringIO(), a fixed width, color_system=None, and force_terminal=False, then assert on the captured string. Check semantic content, row order, and empty states rather than full snapshots, which are brittle across Rich versions.

Create a Table with named columns representing stable fields, add one row per record, and print it through a shared Console. Convert values to explicit strings or Text objects and define empty-state, alignment, and overflow behavior.

Use Progress when task completion is the primary state, such as known iterables or multiple tracked tasks. Use Live when the entire view changes, like a dashboard or updating table. Keep one active live display per console and always use a context manager.

Rich markup is a parser, so strings containing bracket patterns like [red] are interpreted as style tags. Pass untrusted values as Text instances, use rich.markup.escape before interpolation, or pass markup=False for literal strings.

No. When a command supports --json or a pipe protocol, bypass Rich on stdout entirely and emit plain serialization. Rich may still render human-facing errors and diagnostics to a stderr-configured console.

Rich detects non-interactive terminals and disables animated rendering, which is the correct behavior. Do not force terminal or interactive modes into redirected output; accept the plain rendering and emit separate structured logs if a durable audit trail is needed.