[issue45690] Argparse exclusive group inside required exclusive group displays incorrectly

[paul j3]

paul j3 <ajipanca at gmail.com> added the comment:

There was a bug/issue that addressed problems with nested mutually_exclusive_groups.  It should be easy to find.

The problem is that the usage formatter is brittle, building a string and then striping out "unnecessary" characters.  I assume the fix handled the default case (not required), but apparently it missed this variation.

I wasn't too involved with that, since in my opinion nesting these groups is useless, and should be avoided.  You might as well use one union group.  Test the parsing for yourself.

----------
nosy: +paul.j3

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue45690>
_______________________________________