I'm only following this with half a mind at best (sorry), but Bastian had an email that contained:
But I don't think we should rely on everyone using the "#!/usr/bin/env" hack, either: the first python on the path isn't necessarily the right one. The "first python on the path" is the correct thing for the user, otherwise the path is wrong. So "/usr/bin/env pyton" yields the correct interpreter to execute.
Do please remember the problem on Dec Unixes (which appears to be) that if the environment is large (i.e., many environment variables) then /usr/bin/env falls back to *printing* the environment variables, instead of executing the given program (gods know why, but this is Dec). So, for instance, on the Dec Alpha Unix boxes at work here, the #!/usr/bin/env" hack is a consistent failure! (not that I have any *better* suggestion - just don't assume it's a full solution). Tibs -- Tony J Ibbs (Tibs) http://www.tibsnjoan.demon.co.uk/ Give a pedant an inch and they'll take 25.4mm (once they've established you're talking a post-1959 inch, of course) My views! Mine! Mine! (Unless Laser-Scan ask nicely to borrow them.)