On Sat, 3 Dec 2005, Randal L. Schwartz wrote: > >>>>> "Chris" == Chris Devers <[EMAIL PROTECTED]> writes: > > Chris> My understanding is that the Python idiom is to avoid putting the full > Chris> path, in favor of something like > > Chris> #!/usr/bin/env python > > This won't work if env is not in /usr/bin (like say, /bin/env).
Right. My assumption is that the Python idiom must have arisen from a time when the language was new enough that you couldn't depend on it being somewhere like /usr/bin, but (apparently) /usr/bin/env was more likely to exist and to do the right thing. I guess. > Chris> #!env python > > This won't work if env is not in your current directory! (odds on > that, 0% unless you're cd'ed to /usr/bin or /bin, see above.) Right again. I didn't mean to pass this off as "here's what you should do", so much as "here's what I'm cargo-culting from what I've seen in Python examples". :-) -- Chris Devers ¼5£øÜÞÄ
-- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>
