Difference between revisions of "Slicer3:Python:ipython"
From Slicer Wiki
m |
|||
Line 6: | Line 6: | ||
tar xvfz ipython-0.9.1.tar.gz | tar xvfz ipython-0.9.1.tar.gz | ||
cd ipython-0.9.1 | cd ipython-0.9.1 | ||
− | ../../Slicer3-build/Slicer3 --launch .. | + | ../../Slicer3-build/Slicer3 --launch ../python-build/bin/python setup.py install |
</pre> | </pre> | ||
Just a note (inorton): I had a small issue with installation due to md5 import error during setup.py. It looks like stemming from different openssl versions on the Slicer build host machine (this was installing in 3.4 binary distribution for linux). Anyway, got around it by commenting out "import md5" in the offensive utility library: ".../ipython-0.9.1/IPython/external/path.py" md5 is only used in one service routine -- which is not called anywhere else. So should not be a problem, and works fine so far. | Just a note (inorton): I had a small issue with installation due to md5 import error during setup.py. It looks like stemming from different openssl versions on the Slicer build host machine (this was installing in 3.4 binary distribution for linux). Anyway, got around it by commenting out "import md5" in the offensive utility library: ".../ipython-0.9.1/IPython/external/path.py" md5 is only used in one service routine -- which is not called anywhere else. So should not be a problem, and works fine so far. |
Revision as of 15:05, 21 August 2009
Home < Slicer3:Python:ipythonInstall ipython
cd Slicer3-lib wget http://ipython.scipy.org/dist/ipython-0.9.1.tar.gz tar xvfz ipython-0.9.1.tar.gz cd ipython-0.9.1 ../../Slicer3-build/Slicer3 --launch ../python-build/bin/python setup.py install
Just a note (inorton): I had a small issue with installation due to md5 import error during setup.py. It looks like stemming from different openssl versions on the Slicer build host machine (this was installing in 3.4 binary distribution for linux). Anyway, got around it by commenting out "import md5" in the offensive utility library: ".../ipython-0.9.1/IPython/external/path.py" md5 is only used in one service routine -- which is not called anywhere else. So should not be a problem, and works fine so far.