uses both shell and python codes in one script.

[Cameron Simpson]

On 04Oct2019 09:17, Chris Angelico <rosuav at gmail.com> wrote:
>On Fri, Oct 4, 2019 at 9:13 AM Cameron Simpson <cs at cskk.id.au> wrote:
>> If we're going to accept the approach though, I'd rather the shebang 
>> was
>> just "#!/bin/sh". There's _always_ a /bin/sh, and a number of BSDish
>> systems do not have a /usr/bin/env (it tends to land in /bin instead).
>
>My point was that ipython solves nothing. The whole point of merging
>shell and Python was to prepare the environment for the REAL app,
>which is pure Python; so using ipython would add a costly dependency
>without actually helping in any way. Just run it in Python and that's
>that.

+1

Cheers,
Cameron Simpson <cs at cskk.id.au>