Multiple subparsers leads to recursive variables about argcomplete HOT 5 CLOSED

Forgot to say, I just upgraded to the latest and greatest from pip, 0.6.7,

from argcomplete.

Yeah, nested subparsers behave weirdly. When I looked into it, I found that figuring out which subparsers are eligible to receive the next word is really hard, so for now I just throw all subparsers that I can find into the mix of active parsers. If you have a better way to determine active subparsers, by all means please submit a patch. The relevant code is in https://github.com/kislyuk/argcomplete/blob/master/argcomplete/__init__.py#L189.

from argcomplete.

I tried this out and it seems to be fixed. I used version 1.6.0

$ ./testcase.py lookup [tab][tab]
a b c -h --help

$ ./testcase.py lookup a [tab][tab]
env etc -h --help

$ ./testcase.py lookup a env [tab][tab]
aaa -h --help zzz

$ ./testcase.py lookup a env aaa [tab][tab]
-h --help

This looks like correct behavior to me and seems to be inline with what argparse is expecting.

from argcomplete.

Thanks for verifying, @bbejot.

from argcomplete.

@bbejot Would you like to submit a PR for a test case that verifies this? If not I'll add one when I get around to it.

from argcomplete.