Automatically run activate-global-python-argcomplete
See original GitHub issueIt’s very nasty to manually run activate-global-python-argcomplete
. Is it possible to run this automatically on installing the pypi package or the distro (apt, dnf) package?
Issue Analytics
- State:
- Created 8 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
How to set up bash completion — pytest documentation
For global activation of all argcomplete enabled python applications run: sudo activate-global-python-argcomplete. For permanent (but not global) pytest ...
Read more >Ubuntu Manpage: activate-global-python-argcomplete
usage: activate-global-python-argcomplete [-h] [--dest DEST] [--user] Activate the generic bash-completion script for the argcomplete module. optional ...
Read more >argcomplete - PyPI
Activating global completion. The script activate-global-python-argcomplete will try to install the file bash_completion.d/python-argcomplete ...
Read more >Auto-complete does not work for user with argcomplete
Whilst writing this question I found that for python3 I should be using sudo activate-global-python-argcomplete3 followed by exec bash to ...
Read more >Talk:Ansible - ArchWiki - Arch Linux
Running `sudo activate-global-python-argcomplete` tells: ... But I think the package should instead do it automatically.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It might be nice to provide
argcomplete.activate_global_argcomplete
so that packages usingargcomplete
can automatically enable completion if they desire.Thanks for reporting. This is ultimately not the Python package’s choice to make. When running install through setuptools, a Python package generally doesn’t know where its installation destination is, whether it’s being sandboxed in a virtualenv, where the relevant bash-completion installation is, whether installing a global completion hook will trample on another copy of the package, etc.
Conversely, APT (and other system-wide package managers) is in the business of knowing all these things and is in a position to install the global completion hook.
So, please make this request with the distro package maintainers. I’m currently not directly involved in that.