Victor Subervi wrote:
On Mon, Nov 9, 2009 at 2:30 PM, Victor Subervi <victorsube...@gmail.com>wrote:
On Mon, Nov 9, 2009 at 2:27 PM, Rami Chowdhury <rami.chowdh...@gmail.com>wrote:
<snip>
Hold everything. Apparently line-endings got mangled. What I don't
understand is why I didn't see them when I opened the file to edit, and why
they didn't copy and paste when I did that. But dos2unix cleaned up a couple
of files so I presume it will clean up the rest. However, I tried one file,
that reads exactly the same as index.py, and when I surfed to it got a 500
error. Here's what the log said:
<snip>
What I've diagnosed as happening when a python script with Windows
line-ending was posted on my server's cgi environment:
The actual error seemed to be a failure to find the python interpreter,
since some Unix shells take the shebang line to include the \r character
that preceded the newline. Seems to me they could be more tolerant,
since I don't think control characters are likely in the interpreter
file name.
DaveA
--
http://mail.python.org/mailman/listinfo/python-list
