-
-
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] Extra Output Cell Created in Jupyter Notebook when using display #3168
Comments
I commented out that entire block and everything still renders correctly and without the extra output cell but I dont know enough to say its not there for some other very good reason. if self.is_jupyter: # pragma: no cover
pass
#from .jupyter import display
#display(self._buffer, self._render_buffer(self._buffer[:]))
#del self._buffer[:] |
heh, apparently that bit i commented out, while not impacting the |
same issue here, maybe it is problem with jupyter in VSCode. |
That was actually my first thought as well but I was able to reproduce it in the notebook and jupyterlab web interface as well as the jupyterlab standalone application. |
I've got the same problem but only in VSCode (v1.85.1). Output looks normal for Jupyterlab (v3.6.5 ) |
Duplicate of #3329 |
Describe the bug
Here you can see the extra (but empty) output cell between the input and the displayed value.
I actually managed to track it down to this bit here.
https://github.com/Textualize/rich/blob/e9f75c9912ed25b9777bc0257853370951220b17/rich/console.py#L2007C22-L2007C22
The call to display, actually i think its the subsequent call to ipython_display is whats causing the extra cell?
This example is taken from vscode but it also appears in notebooks/jupyterlab.
Platform
Click to expand
What platform (Win/Linux/Mac) are you running on? What terminal software are you using?
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:
If you're using Rich in a Jupyter Notebook, run the following snippet in a cell
and paste the output in your bug report.
The text was updated successfully, but these errors were encountered: