Sam Kerr added the comment:
I was also able to get the stack smashing behavior with the following:
OS: Linux slaptop 4.19.12-arch1-1-ARCH #1 SMP PREEMPT Fri Dec 21 13:56:54 UTC
2018 x86_64 GNU/Linux
GCC: gcc (GCC) 8.2.1 20181127
I was able to track down the issue into the src/x86/ffi64.c
Sam Kerr added the comment:
I fat fingered the example, sorry:
[ [ -opt1 | -opt2 | -opt3 ] | [ [-opt4] [-opt5] [-opt6] ] ]
Note the new pipe between the 2 subgroups
--
___
Python tracker
<http://bugs.python.org/issue22
Sam Kerr added the comment:
What I was going for was the ability to have a group contain a mutually
exclusive group and a non-exclusive group, but using the mutually exclusive
group meant you could not use the non-exclusive group.
Such as:
[ [ -opt1 | -opt2 | -opt3 ] [ [-opt4] [-opt5
New submission from Sam Kerr:
The following code:
import argparse
parser = argparse.ArgumentParser()
group1 = parser.add_mutually_exclusive_group()
group2 = group1.add_mutually_exclusive_group()
group2.add_argument('-hello',action='store_true', he
