When I try to run solaar 'bare' it returns
If I run it as 'python /usr/bin/solaar' it works. solaar has
at its beginning. python is in /usr/bin.

maybe because python is a subset of programming languages like JAVA is it needs its own interpreter to run properly. but that is just off of the cuff.

While I don't have an immediate solution for you, what's happening is that the script is being executed as BASH, not as Python.

What happens if you do this?

And what happens if you do this?

Try:
#!/usr/bin/env python

1 members found this post helpful.

Hi,

c0wb0y is right. will certainly work.

Actually the first line is telling Bash which interpreter to use in order to understand the commands inside the script. Sometimes Bash cannot find python at that location, probably because the python libraries/packages are found under some specific python${VERSION} directory or if there are two versions of python.

However the /usr/bin/env python ensures that python is found.

'which python' returns /usr/bin/python

/usr/bin/python /usr/bin/solaar returns the same as python /usr/bin/solaar

#!/usr/bin/env python doesn't work.

Usually works.

that's not a command, that's something you have to put at the top of your python script.

anyhow, you've been here long enough to know that "doesn't work" isn't an acceptable explanation.

I started a thread on hashbangs about a month ago in the programming forum, asking how they work internally, which led eventually to this Wikipedia article. It seems that it's the exec function called by the shell (or by any other program that forks a script) which makes the decision on what program to launch to interpret the script. But that still doesn't explain why python wasn't found.

Interestingly, the article recommends using "#! /usr/bin/env python" as a hashbang for python scripts because python can be installed in a variety of locations, but that doesn't seem relevant to your problem because you have given an absolute path which is known to be correct.

I donno, did he check his PATH ??? is it within it?

Yes, he says he checked it with which. which only works within your path.

yeah I know it only works if it is in your path, I was being lazy and didn't want to have to read every sticnking post in here. just throwing out a bones. now its going to make me really have to think about it and I do not even program with python.

in his error output it states this

should he not then be looking at that unexpected token that seems to have caused him problems instead of what to write to get python to work?

what is Line 21 what does that line have on it on/in his code page?

I think the need to actually see that code on lines 21 and 24 are in order if as he states it works running it a different way.
or which ever way it is being done, them lines where the error occurs are what one needs to be looking at to see what that code is trying to do in which ever file is throwing them errors ...

Those errors are being thrown because the system is trying to execute the script using bash, not python.

Is the very first line in the file? Nothing above it? No spaces or other characters in there? Was this script written from scratch in a Linux text editor, or did you perhaps copy/paste it from somewhere else or write part of it in Windows? What is the output of

1 members found this post helpful.

Of course I replaced the first line of /usr/bin/solaar with the #!/usr/bin/env solaar - I've been here long enough to know that.

'Doesn't work' means that it behaves exactly as it did before.