Re: [chirp_devel] run_tests: No module named serial
OK, I think the mystery is largely solved. Inside the chirp.app package, I find the following (edited for brevity):
dan[Contents]$ pwd /Applications/_Dans_apps/chirp-daily-20140407.app/Contents dan[Contents]$ ll ... lrwxr-xr-x 1 dan staff 103 Apr 9 13:40 CHIRP -> /opt/kk7ds//Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python
So there's a symbolic link to the "correct" Python inside the package, created about the time I first ran it. (In addition to a fresh hg clone, I thought I'd update my operating bits as well). So where did that link come from?
===================== dan[Contents]$ cat Macos/chirp #!/bin/bash
LOCATION=$(dirname "${BASH_SOURCE}")
PYTHON=/opt/kk7ds//Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python
if [ -x $PYTHON ]; then ln -s $PYTHON "${LOCATION}/../CHIRP" PYTHON=${LOCATION}/../CHIRP export PYTHONPATH="/opt/kk7ds//Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/" else PYTHON=/opt/kk7ds/bin/python2.7 fi
exec "$PYTHON" "${LOCATION}/../Resources/chirp/chirpw" =======================
Looks like somebody decided that the wrong Python was getting used too often, and taught chirp to find the right one and use it.
But no such magic is in place for run_tests. I know how to deal with it.
Thanks for the clues.
-dan
On Apr 9, 2014, at 3:40 PM, Tom Hayward - esarfl@gmail.com wrote:
... ImportError: No module named serial
run_tests is trying to use /usr/bin/python instead of /opt/kk7ds/bin/python. /opt/kk7ds/bin/python is the version that includes python-serial. There are a few ways to resolve this. I'll defer that to someone else (you can probably figure it out).
I'm on a Mac running OS X 10.9.2 Chirp runs ok, it says I'm using (Python 2.7.2).
I'm curious how you are running Chirp ok without python-serial. I have to call Chirp like this on OS X: /opt/kk7ds/bin/python ./chirpw
Sorry I don't have the time to focus on this right now, but here's another hint: http://stackoverflow.com/questions/2429511/why-do-people-write-usr-bin-env-p...
Notice that this is *not* how Dan calls Python from run_tests. You might fix it and submit it as your first bug fix :-)
Tom KD7LXL
On Wed, Apr 9, 2014 at 4:29 PM, chirp.cordless@xoxy.net wrote:
OK, I think the mystery is largely solved. Inside the chirp.app package, I find the following (edited for brevity):
dan[Contents]$ pwd /Applications/_Dans_apps/chirp-daily-20140407.app/Contents dan[Contents]$ ll ... lrwxr-xr-x 1 dan staff 103 Apr 9 13:40 CHIRP -> /opt/kk7ds//Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python
So there's a symbolic link to the "correct" Python inside the package, created about the time I first ran it. (In addition to a fresh hg clone, I thought I'd update my operating bits as well). So where did that link come from?
===================== dan[Contents]$ cat Macos/chirp #!/bin/bash
LOCATION=$(dirname "${BASH_SOURCE}")
PYTHON=/opt/kk7ds//Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python
if [ -x $PYTHON ]; then ln -s $PYTHON "${LOCATION}/../CHIRP" PYTHON=${LOCATION}/../CHIRP export PYTHONPATH="/opt/kk7ds//Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/" else PYTHON=/opt/kk7ds/bin/python2.7 fi
exec "$PYTHON" "${LOCATION}/../Resources/chirp/chirpw"
Looks like somebody decided that the wrong Python was getting used too often, and taught chirp to find the right one and use it.
But no such magic is in place for run_tests. I know how to deal with it.
Thanks for the clues.
-dan
On Apr 9, 2014, at 3:40 PM, Tom Hayward - esarfl@gmail.com wrote:
... ImportError: No module named serial
run_tests is trying to use /usr/bin/python instead of /opt/kk7ds/bin/python. /opt/kk7ds/bin/python is the version that includes python-serial. There are a few ways to resolve this. I'll defer that to someone else (you can probably figure it out).
I'm on a Mac running OS X 10.9.2 Chirp runs ok, it says I'm using (Python 2.7.2).
I'm curious how you are running Chirp ok without python-serial. I have to call Chirp like this on OS X: /opt/kk7ds/bin/python ./chirpw
chirp_devel mailing list chirp_devel@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers
On Wed, Apr 9, 2014 at 4:48 PM, Tom Hayward esarfl@gmail.com wrote:
Sorry I don't have the time to focus on this right now, but here's another hint: http://stackoverflow.com/questions/2429511/why-do-people-write-usr-bin-env-p...
Notice that this is *not* how Dan calls Python from run_tests. You might fix it and submit it as your first bug fix :-)
Tom KD7LXL
Okay, here's what I was hinting but didn't have a chance to type up yesterday:
Add kk7ds python to your path:
PATH=/opt/kk7ds/bin/python:$PATH
Then fix the script so that it runs the first "python" found in your path:
diff -r fa9439f41b37 tests/run_tests --- a/tests/run_tests Wed Mar 19 10:38:45 2014 -0700 +++ b/tests/run_tests Thu Apr 10 10:15:04 2014 -0700 @@ -1,4 +1,4 @@ -#!/usr/bin/python +#!/usr/bin/env python # # Copyright 2011 Dan Smith dsmith@danplanet.com #
Now your system will choose the first "python" found in your PATH, which now is kk7ds python, which includes all the libraries Chirp requires.
Tom KD7LXL
participants (2)
-
chirp.cordless＠xoxy.net -
Tom Hayward