Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #51323 > unrolled thread
| Started by | Ben Finney <ben+python@benfinney.id.au> |
|---|---|
| First post | 2013-07-27 08:08 +1000 |
| Last post | 2013-07-27 08:08 +1000 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Python Script Hashplings Ben Finney <ben+python@benfinney.id.au> - 2013-07-27 08:08 +1000
| From | Ben Finney <ben+python@benfinney.id.au> |
|---|---|
| Date | 2013-07-27 08:08 +1000 |
| Subject | Re: Python Script Hashplings |
| Message-ID | <mailman.5157.1374876519.3114.python-list@python.org> |
Tim Golden <mail@timgolden.me.uk> writes: > Devyn, I'm not a *nix person so someone can point out if I'm wrong, > but my understanding is that the shebang line (or whatever you want to > call it) just tells the shell: run this command to run this file. So > you can put "#!/usr/bin/fish-and-chips" as the first line and it will > try to run the file using /usr/bin/fish-and-chips. Close: it's an instruction not to the shell, but to the kernel. The shell defers any “run the program in this file” to the kernel, and it's the kernel that pays attention to the file's shebang line. -- \ “When cryptography is outlawed, bayl bhgynjf jvyy unir | `\ cevinpl.” —Anonymous | _o__) | Ben Finney
Back to top | Article view | comp.lang.python
csiph-web