no reply from / Invalid Message to kernel (Windows)

[carljv]

Hi,

I've been having an issue with getting vim-ipython to communicate with an IPython kernel. I'm on windows 7, using I believe I've installed everything correctly, and vim is built against the Python on my system (e.g., vim python can import the IPython module, etc.). :source ipy.vim works without errors. But when I start up an IPython kernel, and then call :IPython in vim, I get following errors:

in vim: "no reply from kernel"

in IPython kernel:

[IPKernelApp] Invalid Message Traceback (most recent call last): File "C:\Anaconda\lib\site-packages\IPython\kernel\zmq\ipkernel.py", line 208, in dispatch_shell msg = self.session.unserialize(msg, content=True, copy=False) File "C:\Anaconda\lib\site-packages\IPython\kernel\zmq\session.py", line 722, in unserialize msg_list[i] = msg_list[i].bytes IndexError: list index out of range [IPKernelApp] Invalid Message Traceback (most recent call last): File "C:\Anaconda\lib\site-packages\IPython\kernel\zmq\ipkernel.py", line 208, in dispatch_shell msg = self.session.unserialize(msg, content=True, copy=False) File "C:\Anaconda\lib\site-packages\IPython\kernel\zmq\session.py", line 722, in unserialize msg_list[i] = msg_list[i].bytes IndexError: list index out of range

I'm not exactly sure what the problem is. My Python installation is 2.7.3; IPython is the latest dev version. Python is 32bit, as is vim, I believe -- I'm assuming I wouldn't have gotten this far otherwise).

Thanks for any help or insight,

-c.

[carljv]

Just an update. I'm getting a similar message using MacVim.

[IPKernelApp] Invalid Message Traceback (most recent call last): File "/Users/cvogel/anaconda/lib/python2.7/site-packages/IPython/kernel/zmq/ipkernel.py", line 208, in dispatch_shell msg = self.session.unserialize(msg, content=True, copy=False) File "/Users/cvogel/anaconda/lib/python2.7/site-packages/IPython/kernel/zmq/session.py", line 722, in unserialize msg_list[i] = msg_list[i].bytes IndexError: list index out of range

I suspect there is a 32/64-bit compatibility problem somewhere. But I just wanted to post and see if you had any deeper insight.

Thanks, -c.

[ivanov]

hi carl, there were changes in IPython dev that I didn't keep track of in lock step here in vim-ipython. Now the relevant changes have been merged, can you take a look to see if you're still getting such an error on the latest version of vim-ipython?

[ivanov]

just checking in again, @carljv - do you still see this behavior on the current version of vim-ipython?

[carljv]

Nope. It seems to be working after pulling the latest version. Thanks!

[ivanov]

closing, thanks!