ability to omit the initialization of cli arguments to defaults during inherited initialization

[ovatman]

When working on tomlization of kontrol arguments we needed to remove the default initialization of argument variables. This is required because we would like to override the argument values coming from an input toml with the values from cli which. Default value initialization causes the non specified values from the cli to override specified values from the toml.

However, there are some arguments which are inherited from pyk to which we can not disable the default value initialization from kontrol. It is required to disable such an initialization optionally or when inherited.

[tothtamas28]

Right now cli provides complete ArgumentParser instances, e.g.:

pyk/src/pyk/cli/args.py

Line 16 in e21a9dd

class KCLIArgs:

with arguments like:

pyk/src/pyk/cli/args.py

Line 20 in e21a9dd

args.add_argument('--verbose', '-v', default=False, action='store_true', help='Verbose output.')

One solution for the issue would be to model the command line arguments, and let the user assemble the parser themself.

A bare bones example to illustrate the idea:

cli_arg = (
    ('--verbose', '-v'),
    {
        'default': False,
        'action': 'store_true',
        'help': 'Verbose output.',
    },
)
...
args, kwargs = cli_arg
parser.add_argument(*args, **kwargs)

This should of course be properly modeled with classes that represent the arguments (or groups of them) and expose methods that enable constructing / enriching argument parsers. Then users had the option to exclude an argument, or modify some of their parts (the default in this case).

This would also make it easier to migrate to another argument parser library.

[ehildenb]

See #885

[yale-vinson]

@ovatman What is blocking this one? I want to reference it here so that we know when we can come back to work on this one.

[ovatman]

This PR resolved this issue