-
Notifications
You must be signed in to change notification settings - Fork 226
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
remove broken event loop code #266
Conversation
fixes: matplotlib#79. A potential ipympl specific improvement was mentioned in matplotlib#79 (comment)
@Michael-Equi can you confirm this fixes your issue. You can install with |
That appears to have worked in eliminating the error although pause now seems to be preventing the rendering of my graph in my jupyter lab. |
This pull request introduces 1 alert when merging a03a5cb into 3372f9b - view on LGTM.com new alerts:
|
But not in notebook? Do you have a short example of what you're doing? |
I have tried running this live plot example in both Jupiter land and Jupiter notebook
In both cases it does not render the plot until the final plt.show |
maybe this is similar to: #258 does the solution using async from the stackoverflow post in that issue work for you? As for how to make your example work I think we'll need input from someone with stronger matplotlib skills than me. |
I ended up getting it working with something like the following
|
@ianhi is this ready to be merged? |
I'm not sure. It removes the error in the original issue but #266 (comment) certainly doesn't seem right and I don't think that this is expected behavior for %matplotlib widget
from matplotlib import pyplot as plt
plt.figure()
plt.plot([1,2,3])
plt.pause(2)
plt.plot([3,2,1])
plt.close() compared to the same from ipython: |
So basically I think this removes the error, but doesn't fix the problem. Also, I don't know how to fix the underlying problem, or even what the underlying problem is. |
I see. I wonder if the |
I think this is related to #258 which I also don't really understand. |
Superseded by #291 |
@ianhi really sorry for this, it didn't occur to me that it was the same PR. |
No worries! I had sorta left this one hanging anyways |
Wow, I didn't even check to see if this was here! Sorry! |
fixes: #79
A potential future ipympl specific improvement was mentioned in #79 (comment)