-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bash completion example: unexpected keyword "autocompletion" #966
Comments
It appears that the autocompletion feature was broken Click version 6.7. However, it's now fixed in the latest master branch since 8ac004f. I suppose the fix would come out as part of the 7.0 release |
I checked 6.6 and 6.0 and there's no mention of autocomplete. I don't think it's ever been included in a release. |
Oh right. Agree, it never appeared in the Change Log. |
This feature will be added in 7.0 or later. |
The stock bash completion example here appears to be broken.
Here's my steps to reproduce in a virtualenv:
Now start following the instructions on the readme:
Upon execution of the last statement, however, I see a problem:
This seems to be related to the
autocompletion
kwarg used to decorate thecmd1()
andsubcmd()
methods:In fact, the problem is that the version of click I have does not include bash autocompletion!
(compare to current source).
I have click version 6.7 installed,
The example readme states
I'm a little confused about why bash completion is missing from Click 6.7 when it was added in 2.0!
The text was updated successfully, but these errors were encountered: