Skip to content
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

new figure invoked from a python shell in Emacs for win32 freezes console even after it's closed #2214

Closed
deuscovrigus opened this issue Jul 11, 2013 · 4 comments

Comments

@deuscovrigus
Copy link

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?

@shelper
Copy link

shelper commented Aug 9, 2013

same here
dont know the reason
i reported this on stackoverflow http://stackoverflow.com/questions/17117074/python-shell-in-emacs-freezes-when-using-matplotlib
FYI

@mdboom
Copy link
Member

mdboom commented Aug 12, 2013

You may want to report this in the IPython tracker as well. Not sure where the issue actually lies, but those folks may have additional ideas.

@tacaswell
Copy link
Member

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.

@deuscovrigus
Copy link
Author

Well that did it! Which version of ipython came with the console argument? I know it hasn't been there in the past (prior to v 1.00).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants