bug#67717: 29.1; Eshell doesn't handle script with "#!/usr/bin/env python3 -ESs"

[Jim Porter]

tags 67717 notabug wontfix
thanks

On 12/8/2023 1:34 PM, Sean Devlin wrote:
>  From Eshell, I'm trying to invoke a script with the interpreter line:
>
> #!/usr/bin/env python3 -ESs
>
> Instead of invoking the script, Eshell prints the line:
>
> env: python3 -ESs: No such file or directory

This is the correct behavior. The shebang syntax takes at most 2 values: 
the interpreter, and a single optional argument. Therefore, it's correct 
to interpret "python3 -ESs" as one argument. However, you can fix this 
with the "-S" option to env, e.g. "#!/usr/bin/env -S python3 -ESs". 
(I've confirmed locally that this works properly in Eshell.)

For more information, see here: 
<https://en.wikipedia.org/wiki/Shebang_(Unix)#Character_interpretation>