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
Issues with pyzmq and ipython on EPD update #3524
Comments
PyZMQ issues should only be brought to pyzmq, not IPython. I will close here, and we can continue to dig around in pyzmq. |
Sounds fair. I reported it here as well only because I was not completely sure, it was entirely in pyzmq domain. Especially because the import statements work without error. |
Arg, spoke a bit too soon, before I understood what the issue is. So it looks like it might be a version check bug in IPython. That's weird. Can you try updating IPython (current is 0.13.2, not 0.13.1). |
I see the same output with 13.2. I have attached the log here: |
That's interesting, because you would only get that error message if |
But on Ipython console I get this:
|
Yes, that's why there's something wrong with your path. When you start the notebook, you are not using the same Python or IPython install. |
|
I am sorry, but I am not able to understand how I can use a different ipython when running
and yet another ipython when just adding the argument
|
I'm not sure how it's happening. One thing you might do is edit
to just
This will show you the original error that prevents |
This is the log after changing it to raise. It is now similar to pyzmq import error before installing pyzmq. |
And in a regular Python session: |
|
But now even IPython, shows the same
|
I don't understand, I only changed the raise statement |
If I recall, you said something about building pyzmq inplace. Were you perhaps running IPython from inside the pyzmq build directory before? It sounds like you don't actually have a working pyzmq install. |
Yes, that's my bad. I did build it in-place and was running from the directory before. But if I don't do that, I was getting the error similar to zeromq/pyzmq#162 |
I can run
But that will produce similar results as zeromq/pyzmq#162 |
After you built it in place, did you install it? |
No, I just used
|
I used the above statement followed by install and it appears to be working att start, however, when I open ipython notebook, zmq, keeps throwing Bad address errors. |
That's extremely weird, your zeromq install seems broken in some way. Let's try to get back to a state that makes sense:
|
Thanks for those steps. It did resolve the issue, however, I am still unclear as to what exactly was wrong in the first place. I am particularly concerned that just doing and enpkg --update breaks up things and would like to know if such steps have to be taken for every pyzmq/ipython related update in future. If that is the case then I can hack-up a simple bash script that could be used for future updates. For the record, here is the output log for all steps:
|
You'll probably have to ask Enthought about their update systems. I don't think anything we do should cause that problem. |
Yes, there's definitely nothing to do with IPython here at all. What happened was a strange, incomplete install of pyzmq, either linked against the wrong libzmq or something else. But @takluyver is right, Enthought is the place to ask. |
I had installed EPD python and upgraded it using enpkg --update-all.
It made the following updates: http://pastebin.com/2NmvWHHS
After the update, ipython notebook complains about the pyzmq installation. So based on zeromq/pyzmq#162 , I tried to install pyzmq using the command:
pip install --no-install pyzmq --upgrade and
python setup.py configure --zmq=/usr/local build_ext --inplace
However I still get an error as shown in http://pastebin.com/WKTtALdN.
I have also shown that on running just ipython, it is possible to import zmq, and IPython.zmq. So I am not completely sure if it is IPython/pyzmq issue. If anyone has faced similar issues, I would like to know about it before I go diving in to find some solutions.
The text was updated successfully, but these errors were encountered: