passing arguments to Sage scripts is no longer possible

[yyyyx4]

On Arch Linux, using Sage 10.7, the interpreter throws up when command-line parameters are passed to a script:

$ ./a.sage 42
usage: sage [-h] [-v] [-q] [--simple-prompt] [-V] [-n [{jupyter,jupyterlab}]] [-c [COMMAND]] [file]
sage: error: unrecognized arguments: 42
$ sage a.sage 42
usage: sage [-h] [-v] [-q] [--simple-prompt] [-V] [-n [{jupyter,jupyterlab}]] [-c [COMMAND]] [file]
sage: error: unrecognized arguments: 42

I tried this on a few other machines and it does look like it might be an Arch-specific issue (but it's hard to tell since most other distributions still distribute older versions of Sage). Hence, Cc: @antonio-rojas.

[antonio-rojas]

How do you consume the parameters in your scripts? By sys.argv?

[yyyyx4]

How do you consume the parameters in your scripts? By sys.argv?

Thanks for the quick response! That's indeed what I would like to do, but the script doesn't even begin to execute due to the error above.

[vincentmacri]

Passing arguments works for me with Sage 10.7 on Fedora, although my script uses argparse instead of sys.argv.

[antonio-rojas]

#40872 should fix this