4 ms·
Hello Will, I just wanted to say that rich is a great tool that I'm very appreciative of, and __rich_repr__ is a godsend for debugging datasets without vomitin
by z3c0 4y ago
Hello Will,
I just wanted to say that rich is a great tool that I'm very appreciative of, and __rich_repr__ is a godsend for debugging datasets without vomiting an overload of text into my terminal. Or consolidating spark's awful, multi-language stack traces. Excellent work. Textual is a lot of fun too, and I've been looking forward to this update. Thank you!
- willm 4y agoCheers. Rich repr has become essential in my workflow as well. It's one of those small quality of life things that makes for one less thing to think about.
- newrotik 4y agoCould you elaborate on how you use the tool for the two purposes you mentioned?
- z3c0 4y agoOf course. I use __rich_repr__ to make object representations more succinct[1]. This can also be used to make pretty custom exceptions. You can also use rich.Console.print_exception to output formatted stack traces, with options for including locals, suppressing certain errors, or limiting frames[2]. Pretty great for spark, which usually vomits a novella upon erring. Also, %load_ext rich in a IPython shell to pretty print all output, exceptions or not. [1]: https://rich.readthedocs.io/en/stable/pretty.html#rich-repr-protocol https://rich.readthedocs.io/en/stable/pretty.html#rich-repr-... [2]: https://rich.readthedocs.io/en/stable/reference/console.html#rich.console.Console.print_exception https://rich.readthedocs.io/en/stable/reference/console.html...