Document adding print-completion-script to venv
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
Research direction
Start by reviewing the venv activate script integration point and the existing print-completion-script entry point, using the provided Invoke task as a reference. Clarify which shells and activation paths are supported, then verify that activating a virtual environment makes completion available and that the relevant behavior is covered by tests.
Written by the indexing model from the issue text.
Description
We can also add the print-completion-script to the venv activate script. here an example how to do it with invoke
import os
import pathlib
import sys
import invoke
ROOT_DIR = pathlib.Path(__file__).parent
@invoke.task
def complete(context):
"""Activate the invoke shell completion."""
shell = pathlib.Path(os.environ.get("SHELL", "")).name
completion_script = context.run(
f"invoke --print-completion-script {shell}",
hide=True,
).stdout
with open(".invoke-completion.sh", "w", encoding="UTF-8") as f:
f.write(completion_script)
venv_activate = pathlib.Path(sys.executable).parent / 'activate'
with open(venv_activate, "a", encoding="UTF-8") as f:
f.write(f"\n. {ROOT_DIR / '.invoke-completion.sh'}\n")
- Dominant language
- Python
- Stars
- 4.8k
- Forks
- 412
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from pyinvoke/invoke
-
[Security] Shell injection via Context.cd() path argument — metacharacters not escaped (CWE-78) Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Similar issues
-
agent-ready documentation needs-triage
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 91/100
-
workflow-status page template still says reusable workflows are "triggered only by workflow_call:" Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
instance instance add
Difficulty 1/5 Under an hour Newbie friendliness 72/100
searxng/searx-instances#939 · 1 comment ·
-
area-deployment area-integrations triage:bot-seen
Difficulty 2/5 Half a day Newbie friendliness 86/100