Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

Right click collision for qtconsole in Windows #3002

Open
mayaa6 opened this Issue · 11 comments

5 participants

@mayaa6

I am using ipython for python3.3 in 32bit Windows7. Started the ipython through"ipython3 qtconsole --pylab=inline", the qtconsole will collide immediately when I made a right click in no exception.

@takluyver
Owner
@mayaa6

No error message, and Windows pop a notices saying "python.exe has stop working.". My environment was installed through the following procedure:
1.python3.3 through windows32 binary installer.
2.ipython through windows32 binary installler.
3.ipython's dependence through pip utility.
4.numpy and matplotlib through windows32 binary installer.
PySide was used.

@takluyver
Owner

And does this only occur when you're using pylab?

@mayaa6

yes. ipython3 qtconsole --pylab=inline

@takluyver
Owner

(So, to be clear, it works properly if you just start ipython3 qtconsole, right?)

Thanks for the extra info. It might be a problem with PySide. Beyond that, I don't have any ideas, so it'll have to wait for someone who knows more about Windows.

@mayaa6

I've tried it just now, the same problem occurred when just start ipython3 qtconsole. Through right click is useless in ipython qtconsole, but chances are I misclick and resulting my whole work crashing. It's annoying.

@takluyver
Owner
@simon-b

I experienced the same problem, where "python.exe has stopped working" happened consistenly upon right clicking using qtconsole, with or without --pylab=inline. I removed PySide and installed PyQt4, and it does not happen anymore.

@ivanov
Owner

thanks for the report on the workaround, @simon-b.

Were you able to get around this @mayaa6, or is this still a problem for you?

@mayaa6
@remram44

Couldn't reproduce today (on 64bit Windows 7).

Python 3.3.5 (v3.3.5:62cf4e77f785, Mar  9 2014, 10:37:12) [MSC v.1600 32 bit (Intel)]
ipython==2.3.0
matplotlib==1.4.0
pyside==1.2.2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.