diff options
| author | John Snow <jsnow@redhat.com> | 2023-05-16 12:08:11 +0200 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2023-05-18 08:53:51 +0200 |
| commit | 928348949d1d04f67715fa7125e7e1fa3ff40f7c (patch) | |
| tree | 2d7ffcaddb415abcf3b9a1ecfc8f17528bfa9fbe /python/setup.cfg | |
| parent | 4695a22e9adb0c9a96465109a17da10c17cf2a67 (diff) | |
| download | qemu-928348949d1d04f67715fa7125e7e1fa3ff40f7c.zip qemu-928348949d1d04f67715fa7125e7e1fa3ff40f7c.tar.gz qemu-928348949d1d04f67715fa7125e7e1fa3ff40f7c.tar.bz2 | |
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 <pbonzini@redhat.com>
Signed-off-by: John Snow <jsnow@redhat.com>
Message-Id: <20230511035435.734312-9-jsnow@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'python/setup.cfg')
| -rw-r--r-- | python/setup.cfg | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/python/setup.cfg b/python/setup.cfg index d680374..826a277 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 |