-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Rich shouldn't explode when using more than one display #2712
Comments
I think this issue should at least get some consideration: this is a serious design flaw that hinders the possibility of using Think about it: every time I depend on any package that may use |
Any news about this issue? I'm really struggling with this bug. Almost all my repositories that use rich have this problem and I have to scatter that ugly monkeypatch. |
I am switching back to TQDM, uglier but much more reliable. No one needs fancy graphics if the underlying software is rotting. Clearly |
@LucaBonfiglioli If your only contribution to Open Source is to complain then we're not going to miss you. Best of luck. |
I've encountered this issue too and, after looking into the code, I'm wondering why the code does not use Sure, the configuration of the existing live and the requested configuration of the new progress may not match, but at the moment there does not seem to be any other obvious way to fix rich, and not being usable out-of-the-box across libraries is a pretty major issue... |
Describe the bug
If you use more than one display,
rich
raises an exception (rich.errors.LiveError: Only one live display may be active at once
).A minimal example:
My horrible fix:
I think it shouldn't raise an exception but at most raise a warning. Here I list some reasons:
The text was updated successfully, but these errors were encountered: