Josh Triplett <[EMAIL PROTECTED]> writes: > Package: lintian > Version: 1.23.41 > Severity: normal > > Lintian reports /usr/bin/env as an unusual-interpreter. However, many > python scripts use "#!/usr/bin/env python" to find python on the path > rather than assuming a particular location. Lintian should allow > /usr/bin/env as an interpreter. Better yet, it should special-case > /usr/bin/env and look at the second argument to determine the > interpreter, with a whitelist of permissible env-indirect interpreters; > to start with, that list should include python.
#!/usr/bin/env python is one of the test cases in lintian's test suite, so I'm pretty sure it works in general. lintian's script checking logic already does implement pretty much exactly what you describe. As Chris says, we'll need to see the specific problem that triggered this. -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
