Open andrewbolster opened 9 years ago
:+1: I seem to have the same/similar issue
~$ ldd which python
linux-vdso.so.1 => (0x00007ffd2a3f6000)
libpython2.7.so.1.0 => /home/jb/miniconda/bin/../lib/libpython2.7.so.1.0 (0x00007fdc69fbb000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fdc69d9d000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fdc69b99000)
libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x00007fdc69996000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fdc69690000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fdc692cb000)
/lib64/ld-linux-x86-64.so.2 (0x00007fdc6a39d000)
~$ unset PYTHONPATH ~$ conda update conda
Fetching package metadata: An unexpected error has occurred, please consider sending the following traceback to the conda GitHub issue tracker at:
https://github.com/conda/conda/issues
Include the output of the command 'conda info' in your report.
Traceback (most recent call last):
File "/home/jb/miniconda/bin/conda", line 5, in
~$ conda info Current conda install:
platform : linux-64
conda version : 3.10.1
conda-build version : not installed python version : 2.7.9.final.0 requests version : 2.6.0 root environment : /home/jb/miniconda (writable) default environment : /home/jb/miniconda envs directories : /home/jb/miniconda/envs package cache : /home/jb/miniconda/pkgs channel URLs : https://repo.continuum.io/pkgs/free/linux-64/ https://repo.continuum.io/pkgs/free/noarch/ https://repo.continuum.io/pkgs/pro/linux-64/ https://repo.continuum.io/pkgs/pro/noarch/ config file : None is foreign system : False
Do you have any user site packages in sys.path
(e.g. under /home/jb/.local
)? Are there any .pth
files in there that include /usr/lib
?
thanks - I did find out that there was some remaining "easyinstall" .pth. On a related note, anaconda does not leave the path clean after exiting (contains the anaconda path). It would be great if it did, at the moment I have to remove it manually such that it does not conflict with other things.
@gmarkall Would it be possible if you could clarify your comment? I'm running into the same issue presented by @andrewbolster , and here is my sys.path. There are no .pth
files here, but should I be concerned with all the egg
files or something?
In [3]: sys.path
Out[3]:
['',
'/code/anaconda/bin',
'/code/deep_q_rl/build/pylearn2',
'/home/seita/.local/lib/python2.7/site-packages/PyYAML-3.11-py2.7-linux-x86_64.egg',
'/home/seita/.local/lib/python2.7/site-packages/six-1.10.0-py2.7.egg',
'/usr/lib/python2.7',
'/usr/lib/python2.7/dist-packages',
'/code/anaconda/lib/python27.zip',
'/code/anaconda/lib/python2.7',
'/code/anaconda/lib/python2.7/plat-linux2',
'/code/anaconda/lib/python2.7/lib-tk',
'/code/anaconda/lib/python2.7/lib-old',
'/code/anaconda/lib/python2.7/lib-dynload',
'/home/seita/.local/lib/python2.7/site-packages',
'/code/anaconda/lib/python2.7/site-packages',
'/code/anaconda/lib/python2.7/site-packages/Sphinx-1.3.1-py2.7.egg',
'/code/anaconda/lib/python2.7/site-packages/cryptography-0.9.1-py2.7-linux-x86_64.egg',
'/code/anaconda/lib/python2.7/site-packages/setuptools-18.4-py2.7.egg',
'/usr/lib/python2.7/dist-packages/IPython/extensions']
Note that here is the ldd
output (default python
gives the one in anaconda since I have that in my PATH
variable):
$ ldd /code/anaconda/bin//python
linux-vdso.so.1 => (0x00007fffbd5fc000)
libpython2.7.so.1.0 => /code/anaconda/bin//../lib/libpython2.7.so.1.0 (0x00007f4bedc26000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f4bed9e8000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f4bed7e3000)
libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x00007f4bed5e0000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f4bed2da000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f4becf14000)
/lib64/ld-linux-x86-64.so.2 (0x00007f4bee00b000)
I had a similar issue. The solution for me was changing the line to ENABLE_USER_SITE = False
in ~/anaconda2/lib/python2.7/site.py
.
@rkmaddox - thanks a million ! you solution worked for me :-)
@rkmaddox thank you so much! Why is this happening though? Shouldn't it be OK if one is strictly following the anaconda installing steps?
@rkmaddox thanks! Just leaving a comment here so other people realize there's a simple solution that works...
Thanks so much jbpoline. It worked well
Have seen a few versions of this issue raised before but none of the proposed solutions/checks apply.
Have tried:
This is just after installing
Looks like the correct libpython is being loaded
No pesky PYTHONPATH (apologies for the messy PATH)
Anything else I can do to check this before I go making hacky changes?