Ronan Delacroix

I guess you could do that with ENV or command line options. Use the config file for common options. Then use command line options for overriding the specifics. Also there...

Hi, I'm not sure I have understood everything but it seems to me there are multiple matters to answer here : - Fact that configargparse gives you an error when...

+1 Same problem for me indeed. I'm trying to track down the problem in the code but addind a sub parser definitively breaks something.

I found out that you need to : - set the parser_class parameter on add_subparsers() method, - use the `add_argument` on your command "sub" parser, not on the parent one,...

@AdamLenda is this ticket still open for you?

That's true. Still what do you advice? use logging.info or output nothing?

Fact is logging strongly depends on a custom setup. Real question is : Do we strongly want something to be displayed? - Shall we completely avoid stdout printing and remove...

Yep, agree with you. So I would rather remove print and not change it to logging. No idea how much work is involved here, but simply removing some print statements...

This seems like a bug. If impossible to fix, the difference with argparse behavior should be documented I guess.