Ben Weisburd

When I originally wrote that code, I thought it should work like the --help arg. Is there a reason you can't run the command 2x - once with, once without...

This looks like a bug. I don't immediately see why this is happening, but a PR to fix it would be appreciated.

Unless / until more people request this, perhaps you can implement it by creating your own subclass of ConfigArgParse (or by accessing internal data structures like `self._actions`)? (If you do,...

Sure, a PR would be appreciated.

The current way to provide a list of values (REAMDE section: https://github.com/bw2/ConfigArgParse#config-file-syntax) is a hack that I put in a few iterations prior to adding YAML support. If somebody can...

This is a bug. The problem is at least partly due to https://github.com/bw2/ConfigArgParse/blob/master/configargparse.py#L1032 checking for exact matches without first converting prefixes to their corresponding full option names. A PR to...

Replacing https://github.com/bw2/ConfigArgParse/blob/d8eb8731dfe32125b83d14b9332990af0eb072cc/configargparse.py#L1058-L1060 with ``` return any( arg_name.startswith(potential_arg) for potential_arg in potential_command_line_args for arg_name in arg_names ) ``` should fix this, but argparse has since added an `allow_abbrev` arg, so will...

A pull request would be appreciated.

I did not review that PR carefully enough. If you have time to look in to this - do you see a good way to fix that elif: https://github.com/bw2/ConfigArgParse/commit/8ff6ccad8af1024d9e694f40e7dd69e9cdcc188b#diff-278b05a12fc2a696eef108413d532841R625 ?

I might be misunderstanding the issue, but can you create a script that you run twice - once for dataset1, and once for dataset2? The 1st run would create the...