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

ipengine fails on Windows with "XXX lineno: 355, opcode: 0" #772

Closed
kaazoo opened this Issue Sep 7, 2011 · 3 comments

Comments

Projects
None yet
3 participants
@kaazoo

kaazoo commented Sep 7, 2011

I'm running IPython-0.11 (Python 2.7.2, pyreadline-1.7, pyzmq-2.1.7) on Windows 7 x86. The ipcontroller is running on Mac OSX with Python-2.6 and IPython-0.11. Drive N is mounted via Dokan SSHFS.

When receiving a task, ipengine fails with the following output:

C:\Users\kaazoo>ipengine
[IPEngineApp] Using existing profile dir: u'n:\\ipython\\profile_default'
[IPEngineApp] Loading url_file u'n:\\ipython\\profile_default\\security\\ipcontroller-engine.json'
[IPEngineApp] Registering with controller at tcp://192.168.1.12:59803
[IPEngineApp] Completed registration with id 1
XXX lineno: 355, opcode: 0
@kaazoo

This comment has been minimized.

Show comment
Hide comment
@kaazoo

kaazoo Sep 7, 2011

I upgraded to Python-2.7 on Mac OSX and now the error is gone.

kaazoo commented Sep 7, 2011

I upgraded to Python-2.7 on Mac OSX and now the error is gone.

@kaazoo kaazoo closed this Sep 7, 2011

@minrk

This comment has been minimized.

Show comment
Hide comment
@minrk

minrk Sep 7, 2011

Member

Yes, I think Clients and Engines require the same major/minor Python version, for serialization to be consistent.

Member

minrk commented Sep 7, 2011

Yes, I think Clients and Engines require the same major/minor Python version, for serialization to be consistent.

@andreabedini

This comment has been minimized.

Show comment
Hide comment
@andreabedini

andreabedini Oct 25, 2012

I just run into this problem too. I ended up spending a couple of hours figuring out what the problem was before realizing the engines where using a different python version. Can we have a version check at start ?

andreabedini commented Oct 25, 2012

I just run into this problem too. I ended up spending a couple of hours figuring out what the problem was before realizing the engines where using a different python version. Can we have a version check at start ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment