[PATCH 3/3] patman: fix project-defaults not propagating into parsers

[Simon Glass]

Hi Philipp,

On Wed, 25 Nov 2020 at 06:02, Philipp Tomsich <philipp.tomsich at vrull.eu> wrote:
>
> Simon,
>
> On Wed, 25 Nov 2020 at 00:41, Simon Glass <sjg at chromium.org> wrote:
> > According to the Python documentation and my testing, it should
> > propagate. Do you know what is going wrong here? If there is a
> > problem, we should update the comment.
>
> I don't see any code for propagating this in the argparse module:
>   https://github.com/python/cpython/blob/85c84920f511d0d73a133336daeaf715a022cd64/Lib/argparse.py#L1763
>   https://github.com/python/cpython/blob/85c84920f511d0d73a133336daeaf715a022cd64/Lib/argparse.py#L1363

Thanks for dingging into this.

I'll give it another try and try to figure out why it worked for me,
but I expect I'll find the same problem.

Here is a pointer to the docs I saw:

https://docs.python.org/3/library/argparse.html#argparse.ArgumentParser.set_defaults

"Parser-level defaults can be particularly useful when working with
multiple parsers. See the add_subparsers() method for an example of
this type."

Regards,
Simon