(See also 783259, regarding more flexible python shell
selection.)
I propose that at appropriate times (*), the default
python shell is (re-)determined according to the
sha-bang line.
(*) Suggestions: on file load, on first shell
invocation, on each interactive invocation.
Example of the behaviour I would like:
On loading a file beginning with `#!/usr/bin/env
python2.4', the (default) python shell is set to
`python2.4' (no path information)
On loading a file beginning with
"#!/path/to/my/custom/app", my custom app (with full
path info) is the default shell.
On invoking the shell the first time in a freshly
created file, the sha-bang line is examined and
suggested as a default shell.
(for all cases: if not has sha-bang line: use current
default)
---
I know I'm being a bit vague (sorry); my agenda is
provoking a discussion of the idea (so I'll know what
to implement, diff and submit), not getting a
yes-or-no-p answer.
--Jonas