Closed GoogleCodeExporter closed 8 years ago
Most likely "/home/um/programs/python/lib/python2.6/site-packages/" is not in
Python's module search path.
To check, either type "echo $PYTHONPATH" at the shell prompt or type
import sys
sys.path
at the Python prompt. Perhaps the document at http://docs.python.org/install/
helps
you figure out how to install the module correctly.
Original comment by marcel.m...@tu-dortmund.de
on 11 May 2010 at 9:57
I used the above steps and have got following output:
$echo $PYTHONPATH
$python
Python 2.6.4 (r264:75706, Jan 28 2010, 14:19:59)
[GCC 4.1.2 20071124 (Red Hat 4.1.2-42)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import sys
>>> sys.path
['',
'/home/um/programs/python/lib/python2.6/site-packages/setuptools-0.6c11-py2.6.eg
g',
'/home/um/programs/python/lib/python2.6/site-packages/lxml-2.2.6-py2.6-linux-x86
_64.egg',
'/home/um/programs/python/lib/python26.zip',
'/home/um/programs/python/lib/python2.6',
'/home/um/programs/python/lib/python2.6/plat-linux2',
'/home/um/programs/python/lib/python2.6/lib-tk',
'/home/um/programs/python/lib/python2.6/lib-old',
'/home/um/programs/python/lib/python2.6/lib-dynload',
'/home/um/programs/python/lib/python2.6/site-packages']
>>>
Is this correct?
Original comment by mit...@op.pl
on 12 May 2010 at 11:16
This looks correct. I now realize what happened: You have probably tried to
execute
"import pysam" while you were still in the installation directory (which
contains a
subdirectory named "pysam").
Just go to some other directory, start Python there and try "import pysam"
again.
Original comment by marcel.m...@tu-dortmund.de
on 17 May 2010 at 7:52
Thank you it works.
Original comment by mit...@op.pl
on 18 May 2010 at 10:25
Thanks for providing support!
Original comment by andreas....@gmail.com
on 18 Jul 2010 at 6:03
Original comment by andreas....@gmail.com
on 18 Jul 2010 at 6:04
3# you are so smart!!!
Original comment by farmingt...@gmail.com
on 12 Dec 2014 at 8:42
Thank you
Original comment by mads....@gmail.com
on 28 Jan 2015 at 7:51
Original issue reported on code.google.com by
mit...@op.pl
on 6 May 2010 at 12:41