Ipython-qtconsole (0.12.1) hangs with Python 2.7.3, Windows 7 64 bit

[knorthover]

Upgraded Python to 2.7.3 yesterday and started getting this behavior. Everything had been running fine under 2.7.2

Using the IPython AMD64 0.12.1 build from http://www.lfd.uci.edu/~gohlke/pythonlibs/
IPKernelApp starts up and the console opens and gets as far as printing the
%guiref -> A brief reference about the graphical user interface.

line in the startup sequence but no prompt appears.

ipython starts up fine from the regular DOS command prompt, both in the standard cmd shell and Console2.

[fperez]

Ouch, is there any chance you could test this with a manually installed development version from git? We're getting ready for an 0.13 release, and it would be good to know if this problem exists on Windows still or not. @jstenar, I know you have travel coming up so you may not have time to look into it, but if you know off hand what the situation is, it would be a useful data point...

[jstenar]

Fernando Perez skrev 2012-06-12 21:06:

Ouch, is there any chance you could test this with a manually installed development version from git? We're getting ready for an 0.13 release, and it would be good to know if this problem exists on Windows still or not. @jstenar, I know you have travel coming up so you may not have time to look into it, but if you know off hand what the situation is, it would be a useful data point...

I rarely use the qtconsole so no I do not know.
/Jörgen

[ivanov]

@knorthover - this may be a zeromq-related issue, not necessarily unique to the qtconsole. Does launching ipython console work by itself? (This should start up a two-process ipython where there's a kernel that any client can connect to, and in this case, a terminal-based client which connects to it).

If that does work, it'll print you a message like:

[IPKernelApp] To connect another client to this kernel, use:
[IPKernelApp] --existing kernel-19881.json

update: On second thought, you can just run ipython kernel to get the kernel started up without any clients, and then proceed with what's below...

Then, try to see if ipython qtconsole --existing kernel-19881.json works, to narrow down if it's really a qt issue, or the qt startup code being unable to initialize a kernel, or something else altogether

[knorthover]

Thanks for the very fast responses. I think I have resolved this. It turned out to be embarrasingly simple, I had an old version of the path library in my path and got bitten by the _isdir() issue with 2.7.3. I've updated it with the latest version and it is working fine now.

I apologize for causing all the alarm - what bothered me was that nothing gets reported by the console,