Enrico Forestieri <[EMAIL PROTECTED]> writes:
| On Sat, Jul 15, 2006 at 07:29:41PM +0200, Enrico Forestieri wrote:
|
| > On Sat, Jul 15, 2006 at 09:43:31AM -0500, Bo Peng wrote:
| >
| > > > > I just notice that -tt breaks the #! line so we should not have added
| > > > > -tt to this line.
| > > >
| > > > How? It works here.
| > >
| > > Here is redhat RHEL4, TeXFiles.py generates
| > >
| > > /usr/bin/env: python -tt: no such file or directory.
| >
| > I get the same result on cygwin and debian, but it works on solaris.
| > I suspect a bug in the shebang interpretation on linux (cygwin tries
| > hard to emulate linux) as "/usr/bin/env python -tt" works from the
| > command line.
|
| Hmm... It seems that some *nix kernels do not parse parameters on the
| shebang line, so "python -tt" is passed as a single parameter to the
| env program and it complains for not finding "python -tt" in the PATH.
|
| It seems that FreeBSD and Solaris actually parse the parameters on the
| shebang line. I don't know about other *nices.
|
| All in all, I think that -tt should be replaced by an explicative
| comment as it is pretty useless used in that way.
|
| Alternatively, a python function achieving the same result as -tt on
| the command line could be used. I don't know if such a function exists.
We could run the python scrips through pylint (also as part of
automatic checking.)
--
Lgb
