- How do I log a renderable?
- How do I render console markup in RichHandler?
- Natively inserted ANSI escape sequence characters break alignment of Panel.
- python -m rich.spinner shows extra lines.
- Rich is automatically installing traceback handler.
- Strange colors in console output.
- Why does content in square brackets disappear?
- Why does emoji break alignment in a Table or Panel?
Python's logging module is designed to work with strings. Consequently you won't be able to log Rich renderables (Table, Tree, etc) by calling logger.debug or other similar method.
You could use the capture API to convert the renderable to a string and log that. However I would advise against it.
Logging supports configurable back-ends, which means that a log message could go somewhere other than the terminal -- which may not correctly render the formatting and style produced by Rich.
If you are only logging with a file-handler to stdout, then you probably don't need to use the logging module at all. Consider using Console.log which will render anything that you can print with Rich, with a timestamp.
Console markup won't work anywhere else, other than RichHandler -- which is why they are disabled by default.
See the docs if you want to enable console markup in the logging handler.
If you print ansi escape sequences for color and style you may find the output breaks your output. You may find that border characters in Panel and Table are in the wrong place, for example.
As a general rule, you should allow Rich to generate all ansi escape sequences, so it can correctly account for these invisible characters.
If you can't avoid a string with escape codes, you can convert it to an equivalent Text instance with Text.from_ansi.
The spinner example is know to break on some terminals (Windows in particular).
Some terminals don't display emoji with the correct width, which means Rich can't always align them accurately inside a panel.
Rich will never install the traceback handler automatically.
If you are getting Rich tracebacks and you don't want them, then some other piece of software is calling rich.traceback.install().
Rich will highlight certain patterns in your output such as numbers, strings, and other objects like IP addresses.
Occasionally this may also highlight parts of your output you didn't intend. See the docs on highlighting for how to disable highlighting.
Rich will treat text within square brackets as markup tags, for instance "[bold]This is bold[/bold]".
If you are printing strings with literally square brackets you can either disable markup, or escape your strings. See the docs on console markup for how to do this.
Certain emoji take up double space within the terminal. Unfortunately, terminals don't always agree how wide a given character should be.
Rich has no way of knowing how wide a character will be on any given terminal. This can break alignment in containers like Table and Panel, where Rich needs to know the width of the content.
There are also multiple codepoints characters, such as country flags, and emoji modifiers, which produce wildly different results across terminal emulators.
Fortunately, most characters will work just fine. But you may have to avoid using the emojis that break alignment. You will get good results if you stick to emoji released on or before version 9 of the Unicode database,
Generated by FAQtory