The first line of run_spyceCmd.py is:
#!/usr/bin/env python -u
This doesn't work. Basically the way the shebang line is parsed is:
command (/usr/bin/env), one additional argument that may contain
spaces ("python -u") and then the arguments to run_spyceCmd.py are
passed as the rest of the arguments.
/usr/bin/env: python -u: No such file or directory
This is on Fedora Core 3 Linux, but I'm sure it's the same on any
other UNIX. I would submit a patch, but I don't know why stdin and
stdout need to be unbuffered. There was no -u in 1.3.13. I'm also
not sure how it made it in there, since a UNIX-user must have needed
it, and if someone needed it they would have noticed right away that
it didn't work.
Is there any backstory I should know?