Tony J Ibbs (Tibs) wrote:

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). [snip]

That's not the only problem, apparently different systems are undecided as to whether "env" belongs in "/usr/bin" or in "/bin". Also, considering that other operating systems have their own ways of implementing the spirit of the "#!" hack (and they're usually pretty bad at it), I think the final script really needs to be generated during installation. See this URL for the complete discussion on #!/bin/env: http://x29.deja.com/dnquery.xp?search=next&DBS=1&IS=%22/bin/env%20python%22&ST=QS&offsets=db99p8%021%01db99p1%021%01db2000p1%022%01db99p2%026%01db98p3%024%01db98p4%022%01db99p4%021%01db98p5%021%01db2000p4%021%01db99p5%021%01db99p6%021%01db99p7%024&svcclass=dnserver&CONTEXT=958173312.1618477065 ============================================================================= michaelMuller = mmuller@enduden.com | http://www.cloud9.net/~proteus ----------------------------------------------------------------------------- The natural progress of things is for liberty to yield and government to gain control. - Thomas Jefferson =============================================================================