Subject: Re: [ecasound] reminder about Ecasound Control Interface (fwd)
From: Jack O'Quin (joq_AT_io.com)
Date: Wed Dec 17 2003 - 02:28:09 EET
Kai Vehmanen <k_AT_eca.cx> writes:
> On 15 Dec 2003, Jack O'Quin wrote:
>
> >> #!/usr/bin/env python
> >> from pyeca import *
> > Traceback (most recent call last):
> > File "/home/joq/bin/eci-pos", line 2, in ?
> > from pyeca import *
> > ImportError: No module named pyeca
>
> Run 'python -V' to check the version, and
Python 2.2.3+
So, I picked the wrong option. For some reason, I thought it was 2.1.
The configure didn't detect it automatically. Maybe because I have
more than one version installed? :-/
> python -c "import sys; print (sys.prefix + '/lib/python' + sys.version[:3])"
/usr/lib/python2.2
> Try running 'make install' in ecasound/pyecasound, and see where it
> install the *.py files.
/usr/bin/install -c -d /usr/lib/python2.1/site-packages
/usr/bin/install -c ./eci.py ./pyeca.py ./ecacontrol.py pyecasound.so /usr/lib/python2.1/site-packages
> > I had to `./configure --with-python-modules=/usr/lib/python2.1'.
> > Could this be the problem? Old python interpreter?
>
> Possibly in case the interpreter is looking for modules somewhere
> else...
Exactly right. I should have specified /usr/lib/python2.2.
Thanks for the handholding, Kai!
-- joq
This archive was generated by hypermail 2b28 : Wed Dec 17 2003 - 02:23:12 EET