From 928348949d1d04f67715fa7125e7e1fa3ff40f7c Mon Sep 17 00:00:00 2001 From: John Snow Date: Tue, 16 May 2023 12:08:11 +0200 Subject: mkvenv: add console script entry point generation When creating a virtual environment that inherits system packages, script entry points (like "meson", "sphinx-build", etc) are not re-generated with the correct shebang. When you are *inside* of the venv, this is not a problem, but if you are *outside* of it, you will not have a script that engages the virtual environment appropriately. Add a mechanism that generates new entry points for pre-existing packages so that we can use these scripts to run "meson", "sphinx-build", "pip", unambiguously inside the venv. Signed-off-by: Paolo Bonzini Signed-off-by: John Snow Message-Id: <20230511035435.734312-9-jsnow@redhat.com> Signed-off-by: Paolo Bonzini --- python/setup.cfg | 3 +++ 1 file changed, 3 insertions(+) (limited to 'python/setup.cfg') diff --git a/python/setup.cfg b/python/setup.cfg index d680374b29..826a2771ba 100644 --- a/python/setup.cfg +++ b/python/setup.cfg @@ -119,6 +119,9 @@ ignore_missing_imports = True [mypy-distlib.database] ignore_missing_imports = True +[mypy-distlib.scripts] +ignore_missing_imports = True + [mypy-distlib.version] ignore_missing_imports = True -- cgit 1.4.1