Thanks. I'll check how to make sure this also works for installations into the user directory and then merge it with minor changes.

Alright coming back to this I got to say that I'm not entirely happy since this will probably not work when installing via pip, probably requires sudo when installing, and also installs the file regardless of whether or not bash is even used. I might go down the same route as pip itself (see pip docs) and only keep this for the deb files (since bash is still default for ubuntu/debian).

I'd be in favor of including all (future) shell completion regardless of which shell is being used. It's 1 tiny file per shell that'd allow me to get the full experience if I'd change to or try a different shell.

What is the status on this? As a user I would really appreciate if this gets looked into and merged.

Having all completion files packaged with the program and have a dedicated sub-command to the program CLI that installs the completion for the current shell could be an alternative, but requires more work.