-
Notifications
You must be signed in to change notification settings - Fork 224
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
issue computing repr of Figure
#115
Comments
And there is a timing race here, if you run the second cell with in a second of the first it works ok as the timeout on displaying the "I'm drawing" cursor is not hit. I am testing with master branch IPython, Matplotlib, and ipympl. |
I am not reproducing that issue locally at the moment. Will look more into it tomorrow. |
I think this may require mpl master to reproduce... |
the problem is still there. Looking at @tacaswell link, there seems to be a wired Matplotlib thing "during a save operation we temporarily remove the manager" , that may explain other random un-correct display I have on the widget
|
windows 10 / Python - 3.7.5, and
and
|
reverting #5 makes the thing work again. can it be done as a temporary solution ? |
I think I hit this bug, but now even calling the save right after doesn't help. @tacaswell @SylvainCorlay @stonebig any ideas? |
on a notebook with a %matplotlib widget at first encounter, it seems ok. if before that moment there was a %matplotlib inline, it's not ok. (on unbiased current version of mpl and ipympl) |
I only used |
I have the same problem with %matplotlib widget, and I do not want to switch to inline plotting. Is there a work around? |
I also had the same issue and downgraded my |
I think this is fixed with mpl 3.2.1 |
After updating mpl to version 3.3.0 (and also other packages) I thought it would be gone, but now I have a different exception. My traceback reads as follows:
I haven't seen this AttributeError before. My packages, in case it's helpful:
|
So while mpl 3.3.0 introduced another different exception, mpl 3.2.2. also works. |
Due to matplotlib/matplotlib#10292 during a save operation we temporarily remove the manager
and you will get a traceback that looks like:
I thought we should be going through https://github.com/matplotlib/matplotlib/blob/59b5e0e873dd3420758498c90b15f7f70cb007da/lib/matplotlib/figure.py#L403-L408 but it looks like we are going trough a lambda from IPython core....
I think this could legitimately go against IPython, Matplotlib, or here. Leaving here as the "middle ground" ;)
The text was updated successfully, but these errors were encountered: