Ben Weisburd

you're right, it should print the long option. A pull request / fix would be appreciated.

The `format_values()` method reports where an arg came from. The ignore behavior is not something that many people would want AFAIK.

It's currently somewhat cumbersome but you should be able to do it with ``` def file_open(path, mode="rt"): return open(path, mode, encoding='UTF-8') import configargparse p = configargparse.ArgumentParser(config_file_open_func=file_open) ... ```

The default encoding is platform dependent. I wonder if we should explicitly set the encoding to 'UTF-8'. If anyone has a strong opinion on this, let me know.

If you can submit a PR, it would be much appreciated. I threw in handling for boolean and list values early on (https://github.com/bw2/ConfigArgParse#special-values), in a way that handles simple cases...

If this can be done with a couple lines of code, a PR would be appreciated.

I did intentionally make `default_config_files` always parsed so that you can have them contain default values and then over-ride a subset of the values with a command-line --config file. Have...

configargparse doesn't currently support this. If other people need this usecase, or if you want to add a flag (like `ignore_default_config_files_when_cli_config_file_provided`) in a PR, it could be added. In the...

I think complicated values like this with compound / non-primitive types are too complex for the main configargparse repo. You're welcome to create a subclass or fork of configargparse for...

Yeah, it's needed for the `already_on_command_line(existing_args_list, potential_command_line_args)` check to work - which is a key step in handling args that are for example specified in both on the command-line and...