Description of problem: I have for years used 'ipython -pylab' to interactively plot using matplotlib. Recently, however, interactive plotting no longer works. I cannot say the exact combination of ipython/matplotlib versions of when this broke, but it was in the last three or four months. Version-Release number of selected component (if applicable): $ rpm -q ipython ipython-0.10.1-3.fc13.noarch $ rpm -q python-matplotlib python-matplotlib-0.99.1.2-4.fc13.x86_64 This combination of ipython and matlabplot is the latest available on F13 and it shows the problem. I am not sure about any other versions or combinations of versions. How reproducible: $ ipython -pylab In [1]: import pylab In [2]: pylab.plot([0,1],[1,0]) Out[2]: [<matplotlib.lines.Line2D object at 0x255d390>] Historically after running this command a matplotlib plot would have popped up, but it no longer does. So if you then run pylab.show(), it will pop up, but it blocks and is not interactive as before. Then when you close the plot that popped up, it continues to block. It is hung. After waiting a long time, I hit Ctrl-C, and I get the following message: In [3]: pylab.show() ^CERROR: An unexpected error occurred while tokenizing input The following traceback may be corrupted or invalid The error message is: ('EOF in multi-line statement', (332, 0)) --------------------------------------------------------------------------- KeyboardInterrupt Traceback (most recent call last) /home/lane/<ipython console> in <module>() /usr/lib64/python2.6/site-packages/matplotlib/backends/backend_gtk.pyc in show(mainloop) 76 if mainloop and gtk.main_level() == 0 and \ 77 len(Gcf.get_all_fig_managers())>0: ---> 78 gtk.main() 79 80 def new_figure_manager(num, *args, **kwargs): KeyboardInterrupt: In [4]:
I reverted to ipython-0.10-2.fc13.noarch and it works as it used to.
This is the same like #649281. There is a solution proposed upstream at: https://github.com/ipython/ipython/pull/237 Will test the fix this week and do an update soon...
(In reply to comment #1) > I reverted to ipython-0.10-2.fc13.noarch and it works as it used to. Reverting to ipython-0.10-8.fc14.noarch and python-matplotlib-1.0.0-2.fc14.i686 in Fedora 14 also restores non-blocking plots.
ipython-0.10.2-1.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/ipython-0.10.2-1.fc14
ipython-0.10.2-1.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/ipython-0.10.2-1.fc15
ipython-0.10.2-1.fc13 has been submitted as an update for Fedora 13. https://admin.fedoraproject.org/updates/ipython-0.10.2-1.fc13
Package ipython-0.10.2-1.fc13: * should fix your issue, * was pushed to the Fedora 13 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing ipython-0.10.2-1.fc13' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/ipython-0.10.2-1.fc13 then log in and leave karma (feedback).
ipython-0.10.2-1.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
ipython-0.10.2-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
ipython-0.10.2-1.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
I finally got around to trying this out and the update does solve the problem identified in this bug. THanks.
I tried the update and can verify that it solves my problem. The Android plugin is now working.