Package: python3-virtualenv Version: 20.14.0+ds-1 Severity: normal Dear Maintainer,
when creating a virtual environment without explicitly specifying the Python interpreter, the virtual environment can become unusable, when the default Python version is upgraded with apt. I.e., creating a new virtualenv with virtualenv --prompt 'my_env' venv creates the following links in the directory venv/bin: python -> /usr/bin/python3 python3 -> python python3.10 -> python When the file /usr/bin/python3 will be upgraded to 3.11, then the Python version changes in the virtual environment to 3.11 as well. The locally installed packaged become unusable, since they are installed under "venv/lib/python3.10/site-packages/" It would be much more robust, to specifically link to versioned Python executable, i.e.: python3.10 -> /usr/bin/python3.10 python3 -> python3.10 python -> python Then the user would just need to keep the old Python version installed. Thanks, dietrich -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.16.0-6-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-virtualenv depends on: ii python3 3.10.4-1 ii python3-distlib 0.3.4-1 ii python3-filelock 3.6.0-1 ii python3-importlib-metadata 4.6.4-1 ii python3-pip 22.0.2+dfsg-1 ii python3-pip-whl 22.0.2+dfsg-1 ii python3-platformdirs 2.5.1-1 ii python3-setuptools-whl 59.6.0-1.2 ii python3-six 1.16.0-3 ii python3-wheel-whl 0.37.1-2 python3-virtualenv recommends no packages. Versions of packages python3-virtualenv suggests: pn python2-pip-whl <none> pn python2-setuptools-whl <none> ii python3-wheel-whl [python2-wheel-whl] 0.37.1-2 -- no debconf information
