Relying on environment variables not specifically defined in the CGI documentation is a bad idea, as they may not exist, or could expose bugs in the Web server.  For this reason, all CGI scripts (like the scripts modified by this patch) should use the exact path to the Python interpreter in the #! comment and should not rely on the "env" program (which is still not guaranteed to live in the same place on all systems).

This patch doesn't add anything to the reliability of the scripts; rejected.

Accepted. and assigned to Fred Drake (just because he made the mistake of letting me know he's home <wink>).  Fred, I can't do a sanity-check of this on Windows, so how about just trying it on a system where hash-bang means something?  It's a very simple patch.

note that both the affected files are CGI scripts.
I have a vague feeling that it's done this way on
purpose; if you install a CGI script, you should
make sure you know what "python" you're using...

wait a sec...

http://www.python.org/doc/FAQ.html#4.63

Note -- *don't* do this for CGI scripts. The $PATH
variable for CGI scripts is often very minimal, so
you need to use the actual absolute pathname of the interpreter.

-1 from me, in other words.

reopened; see discussion on python-dev for
more info.