Package: python3-venv
Version: 3.11.2-1+b1
Severity: important
Dear Maintainer,
* What led up to the situation?
1. I installed python3-keystone (openstack identity service)
2. I installed a python program in a virtual environment from
(https://github.com/korcankaraokcu/PINCE) this application installs
keystone-engine (an on-the-fly assembler) via pip into the virtual
environment using the venv module.
* What was the outcome of this action?
When launching pince (in the virtual environment) the keystone package
is loaded from the system path rather than the virtualized path:
[system]: /usr/lib/python3/dist-packages/keystone/__init__.py
[virtual]: <VIRTUALPATH>/lib/python3.11/site-
packages/keystone/__init__.py
* What outcome did you expect instead?
I expected the virtual environment to load the package (keystone) from
the virtual environment and not from the system path.
In other words, priority should be given to loading packages from the
virtual environment (site-packages directory) and never from the system
(dist-packages directory) unless the package does not exist in the
virtual environment.
-- System Information:
Debian Release: 12.8
APT prefers stable-updates
APT policy: (1090, 'stable-updates'), (1090, 'stable-security'), (1090,
'stable-debug'), (1090, 'proposed-updates-debug'), (1090, 'proposed-updates'),
(1090, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.1.0-28-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages python3-venv depends on:
ii python3 3.11.2-1+b1
ii python3-distutils 3.11.2-3
ii python3.11-venv 3.11.2-6+deb12u5
python3-venv recommends no packages.
python3-venv suggests no packages.
-- no debconf information
