You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A newly created figure in the ipython or regular python console in emacs will freeze the figure window. The console is still active and responding to commands but each figure is frozen.
The py-shell-name variable is ipython.bat containing:
If I run ipython.bat from the windows command line there is no abnormal behaviour and the figure window is responsive. . So far it's only occuring within the ipython emacs shell on Windows. I also tried the Tk backend instead of qt with the same result.
I tested this with the same emacs/ipython setup on OS X and it works fine.
It is also, worth mentioning that with ipython 0.10 . and the same emacs setup on Windows the bug does not occur.
I think it's an emacs-eshell related problem along with the changes in the new version of ipython but I can't get a trace for more details. Any suggestions?
The text was updated successfully, but these errors were encountered:
Closing as the linked SO question seems to have a solution which is making sure console is passed to ipython an a cl argument when the interpreter is started.
I have reported this bug on the LP:python-mode project but I think it's independent of python-mode. Here's the description
With the following setup
Ipython 0.13
Emacs 24.1
Windows 7 x64
python-mode.el 6.1.0
ipython.el 2927
matplotlib 1.2.0
A newly created figure in the ipython or regular python console in emacs will freeze the figure window. The console is still active and responding to commands but each figure is frozen.
The py-shell-name variable is ipython.bat containing:
[ipython.bat]
@python.exe -i C:\devel\Python\2.7-bin\Scripts\ipython.py --pylab qt %*
If I run ipython.bat from the windows command line there is no abnormal behaviour and the figure window is responsive. . So far it's only occuring within the ipython emacs shell on Windows. I also tried the Tk backend instead of qt with the same result.
I tested this with the same emacs/ipython setup on OS X and it works fine.
It is also, worth mentioning that with ipython 0.10 . and the same emacs setup on Windows the bug does not occur.
I think it's an emacs-eshell related problem along with the changes in the new version of ipython but I can't get a trace for more details. Any suggestions?
The text was updated successfully, but these errors were encountered: