Current thinking on required options

Dan Stromberg drsalists at gmail.com
Mon Apr 19 12:37:58 EDT 2021


I guess maybe it seems like a problem to someone who hasn't used command
line tools much, based solely on a simplistic interpretation of the
terminology.

But strictly speaking, they're "command line options", or better "command
line arguments", not "options".

On Mon, Apr 19, 2021 at 9:30 AM Paul Bryan <pbryan at anode.ca> wrote:

> Calling them options—when they're required—seems like a problem. 🙂
>
> On Mon, 2021-04-19 at 09:04 -0700, Dan Stromberg wrote:
>
> On Mon, Apr 19, 2021 at 2:55 AM Loris Bennett <loris.bennett at fu-berlin.de>
> wrote:
>
> However, the options -o, -u, and -g are required, not optional.
>
> The documentation
>
>   https://docs.python.org/3/library/argparse.html#required
>
> advises against required options and here
>
>
>
> https://stackoverflow.com/questions/24180527/argparse-required-arguments-listed-under-optional-arguments
>
> a way of adding a section 'required arguments' to the usage is
> described.
>
>
> Of _course_ some options need to be required.
>
> I can't imagine what the author of that page was thinking.
>
>
>


More information about the Python-list mailing list