Kwan, the executable file in question here is not really a script (as I explained in the other mail, I only gave that example because that was the only other time when I saw the same error in bash), but thank you for your insight, I appreciate it.
> This most likely means that the first line of your script is pointing to > > an incorrect executable. Do this: > > which python > > You should get something like /usr/local/bin/python > > Next, check that the first line of the script points to this No, it wasn't this, I typically use "#!/usr/bin/env python" as the first line. > > executable: > > head -1 swatgrs_set Just gives some binary symbols, since it's a compiled executable. > > BTW, this error can also happen if you're using a DOS/Windows python > script that you moved to Linux. The carriage return/linefeed > combination of Windows will need to converted using something like > dos2unix. No, some python scripts I wrote entirely in Linux, moreover, sometimes they'd work ok for some time (with just "./my_script"), then after some more editing they'd refuse to run like that with the same message: "No such file or directory", and I'd have to run them with "python my_script". Thanks, Aleksey
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
