Closed etiennepellegrini closed 1 month ago
Open source maintainers aren't here to listen to you vent.
I'm closing this issue. If you want to try again, without blaming anyone for your misunderstanding, I will consider your request.
I hope we solved your problem.
If you like using Rich, you might also enjoy Textual
Describe the bug
I believe the
rich
documentation should be updated. It presentsrich.print
as a "drop-in replacement forprint
".However, that statement is very misleading, as the developers themselves admit:
After spending several hours tracking down why my output files had extra line breaks, I really wish the differences with
print
were listed in the docs, instead of pretending to be a drop-in replacement. I also would stop recommending people overloadprint
, unless they want surprises later. Had I usedfrom rich import print as rprint
, I probably would have understood thatrich
was responsible much faster.Thanks Etienne
Platform
Click to expand
What platform (Win/Linux/Mac) are you running on? What terminal software are you using? Linux I may ask you to copy and paste the output of the following commands. It may save some time if you do it now. If you're using Rich in a terminal: ``` $ python -m rich.diagnose ╭──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────