I've been tearing my hair out a bit trying to figure why I can't see the
relevant Python modules.
I build Proton on a clean Linux Mint 17 system (which is based on Ubuntu
make all builds successfully and sudo make install installs the following:
fadams@zappa /usr/local/lib/proton/bindings/python $ ls -al
drwxr-xr-x 2 root root 4096 Nov 30 12:28 .
drwxr-xr-x 5 root root 4096 Nov 30 12:20 ..
-rw-r--r-- 1 root root 89278 Nov 30 11:29 cproton.py
-rw-r--r-- 1 root root 103293 Nov 30 12:28 cproton.pyc
-rw-r--r-- 1 root root 103293 Nov 30 12:28 cproton.pyo
-rw-r--r-- 1 root root 1445471 Nov 30 12:20 _cproton.so
-rw-r--r-- 1 root root 109162 Nov 30 11:20 __init__.py
-rw-r--r-- 1 root root 151464 Nov 30 12:28 __init__.pyc
-rw-r--r-- 1 root root 151257 Nov 30 12:28 __init__.pyo
I set PYTHONPATH=/usr/local/lib/proton/bindings/python
but when I try
Traceback (most recent call last):
File "./msgr-recv.py", line 23, in <module>
from proton import *
ImportError: No module named proton
Now I'm thinking that make install hasn't pulled all of the necessary
files into /usr/local/lib/proton/bindings/python the reason I'm thinking
that is when I tried running
I noticed that the PYTHONPATH it created looked like
and this *does* appear to work, the significant bit seems to be the
/home/fadams/qpid/git/qpid-proton/proton-c/bindings/python bit, because
when I tried:
that worked too.
So I'm thinking that the directory proton and its contents in
qpid-proton/proton-c/bindings/python need to be copied to
as part of the make install process too.
Does that seem about right?